A Server by Any Other Name

Thursday Apr 24th 2003 by DatabaseJournal.com Staff
Share:

There are times in every DBAs life when it becomes necessary to change a server name. MAK provides a walk-through for this process with SQL Server 6.5, 7.0 and 2000.

by MAK [Muthusamy Anantha Kumar]

It is imperative to change the server name when infrastructure policy changes, naming convention standard changes or making a standby server the production server (when production server fails). When a server name is changed, SQL server should go through a process to acknowledge and assimilate the change in server name. The process is a little different in different versions. I will walk you through the process for SQL Server 6.5, 7.0 and 2000.

Change Server name:

This task is usually executed by NT/System administrators. Soon after the Network team changes the server name, windows will prompt you to restart the server.

Restart the server.

by MAK [Muthusamy Anantha Kumar]

Process involved in SQL Server 6.5

Step 1 Change client configuration

Open the Client configuration utility and remove the existing connection property.

Select the old server name and click 'remove'

Add the changed server name in the client configuration utility.

Step 2 Register server name

Open Enterprise Manager and remove the existing registration with the old server name. Register the new server name.

Step 3 Update sysservers

Open ISQL/W and run the following statement; it will still display the old server name.

select @@servername

Run the following sql commands.

Use master
go
sp_dropserver 'oldservername'
go
sp_addserver 'changeserver'
go

Step 4: update clients and other servers

Update all of the clients (Follow step1) to point to the new server and any linked server you have updated with the new name. Make sure any user DLLs and web servers pointing to the server name point to the new server name.


by MAK [Muthusamy Anantha Kumar]

Process involved in SQL Server 7.0



Step 1: Ignore error messages

After changing the server and rebooting, you will get the following error messages.




Your SQL Server installation is either corrupt or has been tampered with (unknown package id). Please rerun Setup

Click 'OK'


At least one service or driver failed during system startup. Use Event Viewer to examine the event log for details.

Click 'OK'

Insert the SQL Server CD and run autorun.exe to run Setup.

Step 2 Run SQL Server setup

Click on "Install SQL Server 7.0 Components"

Depending on the SQL server edition that you installed select the edition.

Select "Local Install" and click next.

You will get the following message:

Click "Yes" to continue.

Click 'Finish'

Step 3 Update client network utility

Add the new server name.

Step 4 Register the new server name

Delete the old server registration and register the new server name.

Step 5 Update sysservers

use master
go
Use master
go
sp_configure 'allow updates',1
go
reconfigure with override
go
update sysservers set srvname = 'changeserver' where srvname ='oldservername'
go
sp_configure 'allow updates',0
go
reconfigure with override
go

Step 6 Update sysservers

Use master
go
sp_configure 'allow updates',1
go
reconfigure with override
go
use msdb
go
update sysjobs set originating_server ="oldservername" 
go
sp_configure 'allow updates',0
go
reconfigure with override
go

Note: Usually sysjobs will have the value '(local)' in sysjobs.originating_server column.

Step 7: update clients and other servers

Update all of the clients (Follow step3) to point to the new server and any linked server you have updated with the new name. Make sure any user DLLs and web servers pointing to the server name point to the new server name.


by MAK [Muthusamy Anantha Kumar]

Process involved in SQL Server 2000

SQL Server 2000 recognizes and acknowledges the change in the server name automatically. There are still some simple tweaks involved.



Step 1 Update Client network utility

Step 2 Register the new server name

Delete the old server registration and register the new server name.

Step 3 Update sysservers

use master
go
Use master
go
sp_configure 'allow updates',1
go
reconfigure with override
go
update sysservers set srvname = 'changeserver' where srvname ='oldservername'
go
sp_configure 'allow updates',0
go
reconfigure with override
go

Step 4 Update sysservers

Use master
go
sp_configure 'allow updates',1
go
reconfigure with override
go
use msdb
go
update sysjobs set originating_server ="oldservername" 
go
sp_configure 'allow updates',0
go
reconfigure with override
go

Step 5: update clients and other servers

Update all of the clients (Follow step1) to point to the new server and any linked server you have updated with the new name. Make sure any user DLLs and web servers pointing to the server name point to the new server name.

Conclusion: Though change in the server name is simple and easy, it has complicated effects on the dependant applications, services and components. This article gives a detailed insight of updating SQL server to handle the change in the server name.

Share:
Home
Mobile Site | Full Site
Copyright 2017 © QuinStreet Inc. All Rights Reserved