Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
Michael Valentine Jones
Yak DBA Kernel (pronounced Colonel)
7020 Posts |
 Posted - 2006-03-16 : 17:43:39
|
| I’m getting ready to do some server replacements. The plan is to move the logins, jobs, databases, etc. to the new servers, and then change the names of the old and new servers so that the new server has the same name as the old server.The reason for doing it this way is to minimize the number of changes that will be required to client applications. I figure this will minimize the amount of time that I have to spend playing "cat herder" with our development staff, and let me move the project forward as fast as possible.It’s has been a while since I did a replacement this way, and I was wondering if anyone had a good checklist for this type of switch. Even a partial list or some warnings about gotchas be helpful. This is for SQL Server 2000. Thanks in advance for any assistance.CODO ERGO SUM |
|
|
jen
Master Smack Fu Yak Hacker
4110 Posts |
Posted - 2006-03-16 : 20:37:52
|
| this is a dream migration job... just move the databases with no worries, same setup, same name... just different machine...you can have different approaches to this one, I'm thinking of two less painful waysA. detach the databases and reattach them on the other machine-- for the system databases, I believe you need to do backup and restore still prior to the user databasesB. backup the databases and restore them on the other machinenote: just to be sure, script out all the logins and re-create them on the new machineI did this on one "aging" machine and with only 10 databases to work on, took me 5 working days (inclusive of tests, I like to be thorough on these kind of things)HTH--------------------keeping it simple... |
 |
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
Posted - 2006-03-17 : 01:17:24
|
| If all of the drive letters are the same on both servers then you can detach all databases on the old server, stop the MSSQLSERVER service account on the new server, copy the files over to their proper locations, then start the service. You won't need to transfer jobs, logins, or anything else with this method. Everything will be there. I've done it several times without any problems. The key though is that disk config must be the same between the two servers.After you are done, you can rename the server then run the system stored procedure to fix the rename inside SQL Server, then you should be all set.Tara Kizeraka tduggan |
|
|
|
mr_mist
Grunnio
1870 Posts |
Posted - 2006-03-17 : 03:36:44
|
| Yeah, probably easiest if you build the machine with the intended name, rather than changing it after the event. Watch for sql jobs being linked to the old name if you change it with them in place, this can cause annoyances.-------Moo. :) |
|
|
|
Michael Valentine Jones
Yak DBA Kernel (pronounced Colonel)
7020 Posts |
Posted - 2006-03-17 : 10:01:38
|
| I am planning on bringing over the databases via restore and log shipping, because the drive configurations will change, and I can minimize the amount of time the server is out of service. Also, there will be differences in software levels and SQL versions. Some of the databases will be coming from SQL 7 to 2000, and the SQL Server 2000 patch levels will also be different in some cases, so I am not going to bring over master or msdb, but just migrate logins, dts packages and jobs.I am actually more interested in the best way to handle the actual switch of server names. Anyone have a good procedure for doing that? I cannot build the machine with the intended name, because the old machine will be in use untill shortly before the switch. I just want to make sure the name switch for the physical server and the SQL Server go without a hitch.CODO ERGO SUM |
|
|
|
|
|
|
|
|
Server Replacement Procedure