FIX: Setting Retention Period of a Merge Publication Can Drop Subscriptions

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

SYMPTOMS

When the retention period of a merge publication is modified, all subscriptions of the publication may be dropped.

CAUSE

One or more other publications on the Publisher have their retention periods set to 0 (in other words, the subscription never expires). The problem is caused by the expired subscription clean-up agent when a published database has several publications. The sp_Msdrop_expired_mergesubscription procedure may mistakenly use the retention period of another publication, which never expires, instead of the retention period of the publication that has been modified.

WORKAROUND

If possible, set the retention period of all publications to the same value at the same time.

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.

Properties

Article ID: 283036 - Last Review: February 27, 2014 - Revision: 4.1
APPLIES TO
  • Microsoft SQL Server 7.0 Service Pack 2
  • Microsoft SQL Server 7.0 Standard Edition
  • Microsoft SQL Server 7.0 Service Pack 1
Keywords: 
kbnosurvey kbarchive kbbug kbfix KB283036

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