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)
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:
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:
232570For more information, contact your primary support provider.
(https://support.microsoft.com/kb/232570/ )INF: How to Obtain Service Pack 1 for Microsoft SQL Server 7.0 and Microsoft Data Engine (MSDE) 1.0