Setting the Remote Login Option

You can set a user's remote login option to Trusted or Untrusted mode. Trusted mode specifies that the local server accepts remote logins from other servers and front-end applications without verifying passwords for login IDs. Untrusted mode specifies that passwords are verified before the local server accepts remote logins. The default is Untrusted.

    To specify trusted or untrusted mode

• Type:

  sp_remoteoption [remoteserver, loginame, remotename, optname, {true | false}]

  where

  remoteserver

  Specifies the remote server that has the remote login to which the option should apply.

  loginame

  Is the login name that identified the remote login for the remoteserver, loginname, remotename combination.

  remotename

  Is the remote username that identifies the remote login for the remoteserver, loginname, remotename combination.

  optname

  Is the name of the option that you want to set or unset. Currently, trusted is the only option.

  true | false

  Specifies trusted or untrusted mode. For trusted, use true; for untrusted, use false.

For example, to set the trusted option for chris, type:

sp_remoteoption accounts, salesmgr, chris, trusted, true

The effects of untrusted mode depend on the user's front-end. The isql utility and some front-end applications require that users have the same password on the remote server and the local server. DB-Library applications can be written to allow local users to have different passwords on different servers. For more information, see Microsoft SQL Server Programming DB-Library for C.

If you are configuring for remote access between SQL Servers that have different system administrators, remember that setting trusted mode for the SA allows the remote SA to run all stored procedures, including sp_configure and sp_dboption, on your local server.

For more information about sp_remoteoption, see the Microsoft SQL Server Transact-SQL Reference.