September 30, 2008 at 7:00 pm
I am looking at moving a number of SQL Server 2000 installations from one site to another.
The systems are being moved from the current servers to new equivalent servers in the new site. The new servers will have different names and IP addresses but will have the same level of software installed on them.
Due to the number of systems being moved and the need to minimise the cut-over time I have been considering copying the master, msdb, and model databases from the current servers to the new servers.
So the process would be:
1. Install Windows and SQL Server on the new server to the same level as the current server (using the same drives and folders)
2. Stop SQL Server on current server and new server
3. Copy master, msdb and other system databases from the current server to the same drive/folder on the new server
4. Start SQL Server on new server in single-user mode
5. Run sp_dropserver and sp_addserver to update the SQL Server name
6. Restart SQL Server in normal mode and validate config
Does anyone have any real-life experience of actually doing this and what have I missed?
Thanks in advance for any responses.
Si
October 2, 2008 at 3:01 pm
HI, sounds like a fairly solid plan, here is what I would do and have done before. On the old system I would shut down the sql server, copy all the databases including system dbs. I would then take them to the new server and put the db files in the same path on the new server. Then bring up sql server. As long as your talking about sql 2000 you will not have to worry about the server name change as sql 2000 will take care of this for you, sql 7 would not. The key to success here is making sure the path that is recorded in the master db to your db files and names is the same on the new server. Thats it.
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply