You are currently offline, waiting for your internet to reconnect

Change in SQL Server 2000 for queued updating subscriptions that use Message Queuing

This article has been archived. It is offered "as is" and will no longer be updated.
Microsoft recommends that you use Microsoft SQL Server 2000 queues with queued updating subscriptions for transactional replication. However, if you are running Microsoft Windows 2000 Server on the Distributor and the Subscriber and you have taken steps to help protect your network, you can use Microsoft Message Queuing (also known as MSMQ) as the queuing mechanism at the Subscriber.
If you use Message Queuing, replication creates a queue on the Distributor. The login account that the SQL Server service runs under on the Distributor is granted read permissions and write permissions for the queue, and all the other login accounts are restricted. The login account that the Queue Reader Agent runs under on the Distributor must have read permissions for the queue. The login accounts that the SQL Server service runs under on each Subscriber must have write permissions for the queue. You can handle permissions in one of the following ways:
  • You can use the same login account for the SQL Server service at the Distributor, at all the Subscribers, and for the SQL Server Agent service on the Distributor.
  • You can use different login accounts and grant the appropriate permissions for the queue to each login account.
If you use different login accounts, PeekMessage permissions and Receive Message permissions are required for the Queue Reader Agent. Send Message permissions are required for each Subscriber.

For more information about permissions for Message Queuing, see the "Access control for Message Queuing" topic in Windows 2000 Server Help.

Article ID: 830839 - Last Review: 01/17/2015 05:26:42 - Revision: 2.2

Microsoft SQL Server 2000 Service Pack 3

  • kbnosurvey kbarchive kbinfo KB830839