FIX: Performance Issues with Concurrent Replication Agents and/or High Replication Monitor Refresh Setting (308727)

SYMPTOMS

You may experience performance problems, which manifest as concurrency issues such as deadlocks or excessive blocking, when there are a large number of replication agents running concurrently, or the refresh rate for the Replication Monitor in Enterprise Manager is high.

CAUSE

To either update the status of the Replication Monitor in Enterprise Manager, or to add a history entry in the distribution database, replication agents internally call a stored procedure that is not well-optimized for concurrency.

RESOLUTION

To resolve this problem, obtain the latest service pack for Microsoft SQL Server 2000. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:

290211 INF: How to Obtain the Latest SQL Server 2000 Service Pack

WORKAROUND

To work around the problem either:

Set the refresh in the Enterprise Manager Replication Monitor to a lower value.

-or-
Stagger the execution of your replication agents so that fewer agents run concurrently.

-or-
Decrease the -HistoryVerboseLevel parameter to the replication agent. Lowering this to a value of 0 will reduce the number of new history rows added by the agent, thereby improving concurrency. Refer to SQL Server 2000 Books Online topic "Enhancing Replication Performance" for more information.

STATUS

Microsoft has confirmed that this is a problem in Microsoft SQL Server 2000. This problem was first corrected in Microsoft SQL Server 2000 Service Pack 2.