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 |
|
ras2a
Yak Posting Veteran
66 Posts |
 Posted - 2006-06-23 : 06:52:08
|
| Our current SQL server also acts as Domain Controller. We want to completely move the entire SQL server from this server over to the new server. However, the new (detination) server has a different 'name' than the original server...and we want to retain the new name.I've read the following article about how to move SQL server to a new machine, but it only covers moving to a new machine and keeping the same server name: [url]http://vyaskn.tripod.com/moving_sql_server.htm[/url]Again, we want to move SQL across while retaining the 'new' servers name. What is the easiest/most reliable method to achieve this?This is something I will be doing over a weekend (Sunday) while staff are off...so I have a full day to do it and our main database is only very tiny (260MB)Many thanks for any help you can giveras |
|
|
timmy
Master Smack Fu Yak Hacker
1242 Posts |
Posted - 2006-06-23 : 07:01:59
|
| Should not be a big deal.If you're renaming the server, all you should need to do is update the connection strings of whatever machines are connecting to it. Should take a couple of hours max. Then you can spend the rest of the day in the pub..... |
 |
|
|
ras2a
Yak Posting Veteran
66 Posts |
Posted - 2006-06-23 : 07:04:28
|
quote:
Originally posted by timmy
Should not be a big deal.If you're renaming the server, all you should need to do is update the connection strings of whatever machines are connecting to it. Should take a couple of hours max. Then you can spend the rest of the day in the pub.....
All I want to do is to move the entire SQL install across to the new server...whilst retaining the 'new' server's name. I don't actually want to 'rename' anything.I assume, as you say, that I can just updated our ODBC connections etc to connect to the new server name?cheers mate - appreciate your help. And yeah, a pint or two sounds good afterwards :Dras |
|
|
|
derrickleggett
Pointy Haired Yak DBA
4184 Posts |
Posted - 2006-06-23 : 22:14:42
|
I would also follow this advice in Books Online:quote:
Renaming a ServerWhen you change the name of the computer that is running Microsoft® SQL Server™ 2000, the new name is recognized during SQL Server startup. You do not have to run Setup again to reset the computer name. You can connect to SQL Server using the new computer name after you have restarted the server. However, to correct the sysservers system table, you should manually run these procedures:sp_dropserver <old_name>gosp_addserver <new_name>goIssues with Remote Logins and ReplicationIf the computer has any remote logins, for example, if it is a replication Publisher or Distributor, sp_dropserver may generate an error similar to this:Server: Msg 15190, Level 16, State 1, Procedure sp_dropserver, Line 44There are still remote logins for the server 'SERVER1'.To resolve the error, you may need to drop remote logins for this server. If replication is installed, disable replication on the server before running the sp_dropserver stored procedure.To disable replication using the SQL Server Enterprise Manager Expand a server group, and then expand the Distributor (the server that contains the distribution database).Right-click the Replication folder, and then click Disable Publishing.Complete the steps in the Disable Publishing and Distribution Wizard. ©1988-2000 Microsoft Corporation. All Rights Reserved.
In addition, if you get errors when you try to update jobs that you need to use the master job server, you need to update the originating_server column in the sysjobs table to be the name of the new server.MeanOldDBAderrickleggett@hotmail.comWhen life gives you a lemon, fire the DBA. |
|
|
|
ras2a
Yak Posting Veteran
66 Posts |
Posted - 2006-06-23 : 22:37:23
|
| Wow, speedy responses here. Cheers for that, Derrick |
|
|
|
|
|
|
|
|
Moving SQL to a new machine with 'different' name