You are currently offline, waiting for your internet to reconnect

Your browser is out-of-date

You need to update your browser to use the site.

Update to the latest version of Internet Explorer

FIX: The synchronization process is slow, and the CPU usage is high on the computer that is configured as the Distributor in SQL Server 2005

Extended support for SQL Server 2005 ends on April 12, 2016

If you are still running SQL Server 2005 after April 12, 2016, you will no longer receive security updates and technical support. We recommend upgrading to SQL Server 2014 and Azure SQL Database to achieve breakthrough performance, maintain security and compliance, and optimize your data platform infrastructure. Learn more about the options for upgrading from SQL Server 2005 to a supported version here.

SYMPTOMS
When you synchronize a subscription to a transactional replication publication in Microsoft SQL Server 2005, the synchronization process is slow. During the synchronization process, the CPU usage is high on the computer that is configured as the Distributor.

This problem occurs if the following conditions are true:
  • The MSrepl_commands table contains many rows for the publisher database. For example, the MSrepl_commands table contains 800,000 rows for the publisher database.
  • The synchronization process initializes the Subscriber or reinitializes the Subscriber. Alternatively, you incrementally add an article to the publication before you synchronize the subscription.
Note This problem is not specific to transactional replication in SQL Server 2005. This problem may also occur for any query if the following conditions are true:
  • You query a table that contains many rows. For example, the table contains 800,000 rows.
  • You use the FAST query hint or the TOP query hint in the query.
CAUSE
This problem occurs because SQL Server 2005 generates an inefficient execution plan for one of the queries in the sp_MSget_repl_commands stored procedure. This problem occurs only if the query that performs poorly uses the FAST query hint or the TOP query hint. The execution plan for the query that performs poorly shows that a join predicate is not pushed down to a Clustered Index Seek operator.
RESOLUTION

Service pack information

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

STATUS
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section. This problem was first corrected in SQL Server 2005 Service Pack 3.
MORE INFORMATION
This hotfix introduces trace flag 4126. You must enable this trace flag to resolve this problem. To enable this trace flag, use the DBCC TRACEON statement, or specify trace flag 4126 as a startup parameter for the SQL Server service.

For more information about the same issue that occurs in SQL Server 2000, click the following article number to view the article in the Microsoft Knowledge Base:
929131 FIX: In SQL Server 2000, the synchronization process is slow, and the CPU usage is high on the computer that is configured as the Distributor

For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base:
824684 Description of the standard terminology that is used to describe Microsoft software updates
Properties

Article ID: 959013 - Last Review: 12/16/2008 00:47:03 - Revision: 1.0

  • Microsoft SQL Server 2005 Standard Edition
  • Microsoft SQL Server 2005 Developer Edition
  • Microsoft SQL Server 2005 Enterprise Edition
  • Microsoft SQL Server 2005 Standard X64 Edition
  • Microsoft SQL Server 2005 Standard Edition for Itanium-based Systems
  • Microsoft SQL Server 2005 Enterprise X64 Edition
  • Microsoft SQL Server 2005 Enterprise Edition for Itanium-based Systems
  • Microsoft SQL Server 2005 Workgroup Edition
  • kbtshoot kbsql2005engine kbexpertiseadvanced kbfix kbbug KB959013
Feedback
ation.protocol) + "//c.microsoft.com/ms.js'><\/script>");