What type of migration is this?

Microsoft Windows
SQL Server
It seems like an easy task! All I wanted to do is upgrade my corp system. I had a single Windows Business Server (WBS) 2003 on a high end computer. It failed all the time, due to not enough disk space & slow responce time. I upgraded to 3 new Servers to accomplish all the corp tasks, including SQL, Sharepoint, IIS, Exchange and a couple of new tasks. I have a Windows Server 2003, Windows Server 2003 - Enterprise, & Windows Server 2003 - Web on the three different servers. The Enterprise is the big boy, being the Primary Domain Controller, Exchange Server, & SQL Server. So I am trying to move all the users to this machine, so that I can disable & retire the old WBS server. Now, is there an easy way to have the new server just take over the tasks, so that I can just unplug the old server? Thanks in advance

Answer Wiki

Thanks. We'll let you know when a new response is added.

The first thing that looks very strang to me is that you want to place Exchange and SQL to the same server. Don’t do this (this is a recommendation of microsoft). I thought that the main reason was that those 2 eats all your memory.
I think the best way to do this is to begin with putting your Enterprise Server in the same domain as your old one and make him to take over the roles of your old (DC, …) and also exchange. Your 2003 standard can function as SQL and Sharepoint.

Discuss This Question: 3  Replies

There was an error processing your information. Please try again later.
Thanks. We'll let you know when a new response is added.
Send me notifications when members answer or reply to this question.
  • Petroleumman
    Hello, Yes, you most definitly want to balance your heavy apps by placing SQL and Sharepoint on the 2003 Standard box and make your Enterprise box your DC and Exchange server. This is a must if you desire any kind of performance from your server. SQL and Exchange (both resource hogs) would be a hardware nightmare! As for your transition, if you plan things right it should be pretty seamless. Essentially, once you have your servers built and on the network, create a plan for each task. Remember with Exchange your going to have to update DNS records (internal/external MX, alias, host etc.)and perform complete mailbox moves from one server to another, SQL will require exporting databases, re-establishing links etc. and same with Sharepoint. make sure to test!!! There is a ton of step by step documents available that outline each process so it all goes back to planning. Good luck!
    0 pointsBadges:
  • Platypus
    I'm a little concerned, when you say 'Windows Business Server' do you mean Small Business Server (SBS)? If you were to mean that, that is a whole different ball game. If you did not mean that, and we are just talking one domain and now all of your servers (all 4, I guess?) are in the same domain, I suggest you arrange it so your least powerful server is your primary DC, that does not typically require much load on a box. Spread your Exchange and SQL over the other two servers. Specifically, Microsoft does *not* recommend running Exchange on a DC. Please review some of the best practice recommendations around that. As far as load, SQL can be a memory hog but it depends on the load on your apps. Exchange is *always* a memory pig, it will want to essentially consume all available memory. It will give it up to other apps, but just that operation will tend to make the other apps lag a bit. David
    20 pointsBadges:
  • Ehcraig
    Thanks for all your suggestions. The type of migration, is a Windows Small Business Server (SBS) to Windows Server 2003 (WS2K), and it has been a real challenge. I did take all your advice and installed the SQL Server on the WS2K - Std. Now I need to migrate all the data from the SQL on the SBS & from the SQL on the WS2K - Enterprise to the new one on the WS2K - Std. After that, then the real challenge begins as I start to plan for the WS2K to take over & the SBS to come down. Evans
    0 pointsBadges:

Forgot Password

No problem! Submit your e-mail address below. We'll send you an e-mail containing your password.

Your password has been sent to:

To follow this tag...

There was an error processing your information. Please try again later.

Thanks! We'll email you when relevant content is added and updated.


Share this item with your network: