Security for Immediate-updating Subscribers

The Immediate-updating Subscribers option supports either dynamic RPC mode or static RPC mode for the 2PC connection from the synchronization triggers back to the Publisher. In dynamic RPC mode, synchronization triggers connect dynamically to the Publisher, using a supplied server name, login, and password. This mode offers increased security for users who do not want a statically-defined linked server/remote server connection from a Subscriber to Publisher. It is also easier to use when setting up push subscriptions because the Publisher does not have to be predefined at the Subscriber. In static RPC mode, synchronization triggers connect to the Publisher over a statically-defined server name defined as a linked server or remote server in the sysservers table. This entry is added by an administrator at the Subscriber server.

The configuration mode is set automatically when creating push or pull subscriptions:

When using dynamic RPCs, Microsoft® SQL Server™ handles login and password forwarding by adding a replication command to the distribution database to call sp_addsynctriggers at the Subscriber. The login and scrambled password are passed as parameters to the stored procedure. When executed at the Subscriber, sp_addsynctriggers creates immediate-updating triggers and configures the linked server connection.

When executed at the Publisher, the immediate-updating Subscriber stored procedures check the publication access list (PAL) to ensure that the user account executing the remote procedure call (RPC) has permissions to update the data in the publication.

\

See Also

sp_addsynctriggers


(c) 1988-98 Microsoft Corporation. All Rights Reserved.