FIX: Merge Metadata Cleanup May Cause Subscriber Transaction Log to Grow Quickly

Article translations Article translations
Article ID: 300056 - View products that this article applies to.
This article was previously published under Q300056
BUG #: 352358 (SHILOH_BUGS)
Expand all | Collapse all

SYMPTOMS

When running the merge cleanup process (sp_mergecleanupmetadata), the merge subscribing database may be unable to truncate the transaction log until the merge cleanup process finishes.

CAUSE

The merge cleanup process starts a new transaction when running metadata cleanup on the subscriber. Because this transaction stays open during the cleanup process, the log cannot be truncated until the cleanup process finishes.

RESOLUTION

To resolve this problem, obtain the latest service pack for 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

STATUS

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

MORE INFORMATION

This behavior occurs only in merge subscribing databases. In merge publishing databases, metadata deletes are committed in batches of 5000 rows; therefore, the publishing database is not affected by this behavior.

Properties

Article ID: 300056 - Last Review: November 5, 2003 - Revision: 3.2
APPLIES TO
  • Microsoft SQL Server 2000 Standard Edition
Keywords: 
kbbug kbfix kbsqlserv2000sp1fix KB300056

Give Feedback

 

Contact us for more help

Contact us for more help
Connect with Answer Desk for expert help.
Get more support from smallbusiness.support.microsoft.com