Renaming a Server
When 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 GO sp_addserver new_name, local GO
When you have more than one instance of SQL Server on the computer, change the sysservers system table information by running the stored procedures this way:
sp_dropserver old_servername\instancename GO sp_addserver new_servername\instancename, local GO
Issues with Remote Logins and Replication
If 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 44 There 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.