SST Operations Bridge Troubleshooting Guide, Version 1.1

Troubleshooting SST/OB Database 23

For a renamed computer that hosts a named instance of SQL Server, run the following procedures:

sp_dropserver <old_name\instancename>

sp_addserver <new_name\instancename>, local

Restart the instance of SQL Server.

After a computer has been renamed, any connections that used the old computer name must connect by

using the new name.

To verify that the renaming operation has completed successfully, select information from either

@@SERVERNAME or sys.servers. The @@SERVERNAME function will return the new name, and the

sys.servers table will show the new name. The following example shows the use of @@SERVERNAME.

SELECT @@SERVERNAME AS 'Server Name'

Additional Considerations

Remote Logins - If the computer has any remote logins, running sp_dropserver might generate an error

similar to the following:

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 must drop remote logins for this server.

To drop remote logins

For a default instance, run the following procedure:

sp_dropremotelogin old_name

For a named instance, run the following procedure:

sp_dropremotelogin old_name\instancename

Linked Server Configurations - Linked server configurations will be affected by the computer renaming

operation. Use sp_addlinkedserver or sp_setnetname to update computer name references. For more

information, see the sp_addlinkedserver (Transact-SQL) or sp_setnetname (Transact-SQL) SQL Server Books

Online topic on MSDN.

Client Alias Names - Client aliases that use named pipes will be affected by the computer renaming

operation. For example, if an alias "PROD_SRVR" was created to point to SRVR1 and uses the named

pipes protocol, the pipe name will look like \\SRVR1\pipe\sql\query. After the computer is renamed, the

path of the named pipe will no longer be valid and. For more information about named pipes, see the

Creating a Valid Connection String Using Named Pipes SQL Server Books Online topic on MSDN.

Troubleshooting SST/OB

Database