June 22, 2009 at 11:46 am
So our production box is almost done. We would like to migrate it to another server. What are the best practices for this type of task? I have to move databases, log ins, and DTS packages.
Thanks,
Chad
June 22, 2009 at 12:16 pm
Script the logins and roles, back up the databases and restore them on the new server, and you can either do the same with msdb (for DTS packages and jobs), or you can have SQL migrate them for you since it has a wizard for that in Enterprise Manager.
The key thing is, move them, test them, test the applications, but keep the old server available till you've done all the testing you need. It's sometimes easier to bring the old server back online than to fix a whole bunch of migration errors.
Another option, if your storage allows it, is to set up the new server, and move the old storage into it physically. If, for example, your databases and such are on a SAN, you can attach the old SAN to the new server. If they're on internal hard drives, you might be able to move those.
If restoring msdb onto the new server isn't an option, something you might want to look into is either a second instance of SQL Server, on the new hardware, with the old databases, or a virtual machine on the new hardware.
- Gus "GSquared", RSVP, OODA, MAP, NMVP, FAQ, SAT, SQL, DNA, RNA, UOI, IOU, AM, PM, AD, BC, BCE, USA, UN, CF, ROFL, LOL, ETC
Property of The Thread
"Nobody knows the age of the human race, but everyone agrees it's old enough to know better." - Anon
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply