FIX: Update Generation Markers After Applying the MSmerge_genhistory.bcp

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

SYMPTOMS

After synchronization, the generation markers are not updated, which causes the first run of the merge agent to take a long time to finish because it starts processing from generation id 1. The fix involves processing the schema changes at the subscriber to set the last received and last sent generation markers in the MSmerge_replinfo table.

CAUSE

The initial synchronization propagates MSmerge_genhistory.bcp to the subscriber. The first merge process after the initial synchronization starts checking for generations from number 1 even if there have been many generations created at the publisher before the synchronization process.

STATUS

Microsoft has confirmed this to be a problem in SQL Server 7.0. This problem has been corrected in U.S. Service Pack 2 for Microsoft SQL Server 7.0. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
254561 INF: How to Obtain Service Pack 2 for Microsoft SQL Server 7.0 and Microsoft Data Engine (MSDE) 1.0
For more information, contact your primary support provider.

Properties

Article ID: 250994 - Last Review: October 20, 2013 - Revision: 6.1
APPLIES TO
  • Microsoft SQL Server 7.0 Service Pack 1
  • Microsoft SQL Server 7.0 Standard Edition
Keywords: 
kbnosurvey kbarchive kbbug kbfix KB250994

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