| title | sp_addremotelogin (Transact-SQL) | Microsoft Docs | ||
|---|---|---|---|
| ms.custom | |||
| ms.date | 03/14/2017 | ||
| ms.prod | sql | ||
| ms.prod_service | database-engine | ||
| ms.reviewer | |||
| ms.technology | system-objects | ||
| ms.topic | language-reference | ||
| f1_keywords |
|
||
| dev_langs |
|
||
| helpviewer_keywords |
|
||
| ms.assetid | 71b7cd36-a17d-4b12-b102-10aeb0f9268b | ||
| author | VanMSFT | ||
| ms.author | vanto |
[!INCLUDEtsql-appliesto-ss2008-xxxx-xxxx-xxx-md]
Adds a new remote login ID on the local server. This enables remote servers to connect and execute remote procedure calls.
Important
[!INCLUDEssNoteDepNextDontUse] Use linked servers and linked server stored procedures instead.
Transact-SQL Syntax Conventions
sp_addremotelogin [ @remoteserver = ] 'remoteserver'
[ , [ @loginame = ] 'login' ]
[ , [ @remotename = ] 'remote_name' ]
[ @remoteserver = ] 'remoteserver'
Is the name of the remote server that the remote login applies to. remoteserver is sysname, with no default. If only remoteserver is specified, all users on remoteserver are mapped to existing logins of the same name on the local server. The server must be known to the local server. This is added by using sp_addserver. When users on remoteserver connect to the local server that is running [!INCLUDEssNoVersion] to execute a remote stored procedure, they connect as the local login that matches their own login on remoteserver. remoteserver is the server that initiates the remote procedure call.
[ @loginame = ] 'login'
Is the login ID of the user on the local instance of [!INCLUDEssNoVersion]. login is sysname, with a default of NULL. loginmust already exist on the local instance of [!INCLUDEssNoVersion]. If login is specified, all users on remoteserver are mapped to that specific local login. When users on remoteserver connect to the local instance of [!INCLUDEssNoVersion] to execute a remote stored procedure, they connect as login.
[ @remotename = ] 'remote_name'
Is the login ID of the user on the remote server. remote_name is sysname, with a default of NULL. remote_name must exist on remoteserver. If remote_name is specified, the specific user remote_name is mapped to login on the local server. When remote_name on remoteserver connects to the local instance of [!INCLUDEssNoVersion] to execute a remote stored procedure, it connects as login. The login ID of remote_name can be different from the login ID on the remote server, login.
0 (success) or 1 (failure)
To execute distributed queries, use sp_addlinkedsrvlogin.
sp_addremotelogin cannot be used inside a user-defined transaction.
Only members of the sysadmin and securityadmin fixed server roles can execute sp_addremotelogin.
The following example maps remote names to local names when the remote server ACCOUNTS and local server have the same user logins.
EXEC sp_addremotelogin 'ACCOUNTS';
The following example creates an entry that maps all users from the remote server ACCOUNTS to the local login ID Albert.
EXEC sp_addremotelogin 'ACCOUNTS', 'Albert';
The following example maps a remote login from the remote user Chris on the remote server ACCOUNTS to the local user salesmgr.
EXEC sp_addremotelogin 'ACCOUNTS', 'salesmgr', 'Chris';
sp_addlinkedsrvlogin (Transact-SQL)
sp_addlogin (Transact-SQL)
sp_addserver (Transact-SQL)
sp_dropremotelogin (Transact-SQL)
sp_grantlogin (Transact-SQL)
sp_helpremotelogin (Transact-SQL)
sp_helpserver (Transact-SQL)
sp_remoteoption (Transact-SQL)
sp_revokelogin (Transact-SQL)
System Stored Procedures (Transact-SQL)