Article ID: 280808
Article Last Modified on 3/14/2006
APPLIES TO
- Microsoft SQL Server 7.0 Standard Edition
This article was previously published under Q280808
BUG #:58160 (SQLBUG_70)
SYMPTOMS
When there is a pull subscription created from SQL Server 7.0 for a merge publication in SQL Server 2000, the merge agent successfully applies a snapshot even if the snapshot has expired. No error is returned, although the snapshot has passed the retention period.
CAUSE
SQL Server 7.0 does not check for obsolete snapshots.
STATUS
Microsoft has confirmed this to be a problem in SQL Server 7.0. This problem has been corrected in U.S. Service Pack 3 for Microsoft SQL Server 7.0. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
274799 INF: How to Obtain Service Pack 3 for Microsoft SQL Server 7.0 and Microsoft Data Engine (MSDE) 1.0
For more information, contact your primary support provider.
MORE INFORMATION
Steps to Reproduce the Behavior
- In SQL Server 2000, publish the Authors table in the Pubs database.
- Check the Merge Retention Period; by default, it will be 14 days. This value is set in the publication properties on the General tab.
- Run the snapshot agent to generate the snapshot files.
- Stop SQL Server, advance the system date beyond the retention period, and then restart SQL Server.
- On a computer running SQL Server 7.0, create a pull subscription to this publication.
- Run the merge agent. The snapshot is applied successfully.
In SQL Server 7.0 Service Pack 3, this problem has been corrected. If the merge agent is run and the snapshot is obsolete, the merge agent fails with the following error:
Additional query words: Snapshot, Obsolete, Merge
Keywords: KB280808
