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

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.

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

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.

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: For more information, contact your primary support provider.