January 23, 2004 at 8:18 am
We have a SQL Server named SERVERA
We are building a new server to replace SERVERA. This new machine has to be named something different during the build. The new server's name is SERVERB.
I have to install SQL Server on SERVERB.
My question is, when they change the name of SERVERB to SERVERA, what do I have to do to make SQL Server work properly.
I am running SQL Server 2K, SP3 + a hotfix.
Thanks!
----------------------------------------------------------01010011010100010100110000100000010100110110010101110010011101100110010101110010001000000101001001101111011000110110101101110011
January 23, 2004 at 9:19 am
There is an easy answer to this.... but it escapes me for the moment...
Someone will post it... it has to do with the master.sysservers table entry etc... only takes a second to do.
However, you may want to hold off doing (post install) SQL work on SERVERB before you get the named switched back to SERVERA. Get's more complicated if things like SQL Jobs are created while the server is named SERVERB, then renamed to SERVERA.
Once you understand the BITs, all the pieces come together
January 23, 2004 at 9:58 am
Rename the Windows server.
Inside SQL run:
sp_dropserver serverb
sp_addserver servera, local
January 23, 2004 at 11:21 am
Thanks Steve, I don't do it often enough to retain it in my ever deteriorating brain cells. It's tough getting older.
Once you understand the BITs, all the pieces come together
January 25, 2004 at 6:18 pm
Couple other points, if you have created any jobs under the old servername and want to retain them you will have to update the originating server in the MSDB database, sysjobs table.
Also, make sure the SQL service gets added to the new servername to be able to log onto.
HTH
------------
Ray Higdon MCSE, MCDBA, CCNA
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply