FIX: Restore to New Server Causes Transactions to Remain in Log

Article translations Article translations
Article ID: 198514 - View products that this article applies to.
This article was previously published under Q198514
This article has been archived. It is offered "as is" and will no longer be updated.
BUG #: 53311 (SQLBUG_70)
Expand all | Collapse all

SYMPTOMS

Restoring a backup of a published database onto a server that does not have replication installed causes the transactions that are marked for replication to remain in the transaction log. This prevents the log from truncating and can cause the log files to grow.

CAUSE

The problem occurs because when the published database was restored, it did not clear the log of transactions that were marked for replication.

WORKAROUND

You can use one of the following methods to work around this problem:
  • Enable the target database for publishing prior to restoring it. If the target database will not be published, it can then be unpublished using the replication tools included with SQL Server Enterprise Manager.

    -or-
  • If possible, unpublish the source database prior to starting the backup.

STATUS

Microsoft has confirmed this to be a problem in SQL Server 7.0. This problem has been corrected in U.S. Service Pack 1 for Microsoft SQL Server 7.0. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
232570INF: How to Obtain Service Pack 1 for Microsoft SQL Server 7.0 and Microsoft Data Engine (MSDE) 1.0
For more information, contact your primary support provider.

Properties

Article ID: 198514 - Last Review: October 11, 2013 - Revision: 2.1
APPLIES TO
  • Microsoft SQL Server 7.0 Standard Edition
Keywords: 
kbnosurvey kbarchive kbbug kbfix KB198514

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