ALIASING REMOTE SERVERS

What can you do if you can't add a linked server because there's 
already
a server name listed as a remote server or you can't add a remote 
server
because there's already a linked server with the same name? The 
solution
is to add a remote server with an alias network server name. Use the
following script as an example:

-- The current session is on ServerB with  issues for ServerA.
-- Drop server if a remote server.

exec sp_dropserver @server = ServerA

Add the remote server's new alias name.

exec sp_addserver @server = ServerA_remote

Change the remote server's network name to the real server's name.

exec sp_setnetname @server = ServerA_remote,
@netname = ServerA

Add the linked server.

exec sp_addlinkedserver @server = ServerA

Verify the server is listed as both a linked and aliased remote server.

exec sp_helpserver

Note: Because the sp_setnetname is used, the remote server cannot be
used in distributed transactions due to the aliasing. Therefore, using 
the
remote server name, ServerA_remote, in a distributed transaction will
fail; however, using the linked server name, ServerA, in a distributed
transaction will not fail.

Follow these steps to ensure that the servers recognize one another:


1. Add ServerB as a remote server on ServerA so that the servers
recognize one another; this is the nature of adding remote servers for 
backward
compatibility. Linked servers are recommended over remote servers since
they allow for queries against the linked server, as well as remote 
stored
procedure calls. Remote servers only allow for the execution of remote
procedures.

2. Add remote logins to both ServerA and ServerB. This, too, is
necessary when adding remote servers (due to backward compatibility): 
ServerA
must recognize ServerB and vice versa.


The login used for the local server must be a valid login on the remote
server for the remote stored procedure to be executed (for either 
remote
or linked servers). In addition, the remote login must be granted the
appropriate permissions to successfully execute the stored procedure.

----------------------------------------