The RemoteServers collection contains RemoteServer objects that expose the attributes of an instance of Microsoft® SQL Server™ visible as a remote server.
SQL Server provides several mechanisms to help manage connections between instances of SQL Server in an organization. One mechanism is remote-server naming.
An instance of SQL Server can maintain authentication information for connections originating from other instances of SQL Server. Each instance of SQL Server in an organization can control access by listing instances of SQL Server from which it accepts connections.
Additionally, when a remote server is named at an instance of SQL Server, the server maintaining the name list can, in turn, originate a connection to a named remote server.
Note Remote server naming is one method for configuring server-initiated access for instances of SQL Server in an organization. SQL Server version 7.0 implements distributed queries using persisted OLE DB data source definitions called linked servers. For more information, see LinkedServer Object.
With the RemoteServers collection, you can:
To identify an instance of SQL Server as a remote server
To remove a named remote server, disabling access to or from the instance
oSQLServer.RemoteServers.Remove("LONDON1")
To rename an instance of SQL Server
When using the Item or Remove method, the RemoteServers collection supports member identification using either name or ordinal reference syntax. For example:
Set oRemoteServer = oSQLServer.RemoteServers("SEATTLE2")
Or:
Set oRemoteServer = oSQLServer.RemoteServers(2)
Note Creating or removing remote server entries by using the RemoteServers collection requires appropriate privilege. The SQL Server login used for SQLServer object connection must be a member of the fixed role setupadmin or a role with greater privilege.