RemoteLogins Collection (SQL-DMO)

The RemoteLogin object exposes the properties of a single login mapping record for connections to a Microsoft® SQL Server™ installation originating from another, known SQL Server installation.

Remarks

A SQL Server installation can maintain authentication information for connections originating from other SQL Server installations. Server-originated connections are attempted when, for example, remote procedure calls are part of a Transact-SQL script.

Each SQL Server installation in an organization can control access by listing the servers it accepts connections from. For each of these remote servers, login-identifier mappings specify the local login used by a remote server connection when that remote server connects as part of a process run by the remote login.

With the RemoteLogins collection, you can:

• Map a login record on one SQL Server installation to an existing login record on another SQL Server installation.
• Remove a remote login record from the list of logins mapped for the remote SQL Server installation.

To create a remote login

1. Create a RemoteLogin object.
2. Configure the RemoteLogin object by setting the RemoteName property to the name of a login on the remote (or connecting) SQL Server installation.
3. Configure the RemoteLogin object by setting the LocalName property to the name of a login on the local (or connected to) SQL Server installation.
4. Add the RemoteLogin object to the RemoteLogins collection of a RemoteServer object referencing an existing remote server definition.

To remove a remote login

• Use the Remove method of the RemoteLogins collection as in:

    oRemoteServer.RemoteLogins.Remove("stevenb")

When using the Item or Remove method, the RemoteLogins collection supports member identification using either name or ordinal reference syntax. For example:

Set oRemoteLogin = oRemoteServer.RemoteLogins("stevenb")

Or:

Set oRemoteLogin = oRemoteServer.RemoteLogins(2)

Note Creating or removing remote server login mappings by using the RemoteLogins collection requires appropriate privilege. The SQL Server login used for SQLServer object connection must be a member of the fixed role securityadmin or a role with greater privilege.

Methods

Properties

Count Property