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

• Microsoft SQL Server version 7.0

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 version 7.0. This problem has been corrected in U.S. Service Pack 1 for Microsoft SQL Server version 7.0. For information about downloading and installing the latest SQL Server Service Pack, see http://support.microsoft.com/support/sql/.

For more information, contact your primary support provider.

Additional query words: prodsql

Keywords          : kbbug7.00 
Version           : winnt:7.0
Platform          : winnt 
Issue type        : kbbug 

Last Reviewed: June 7, 1999