Microsoft KB Archive/239015

= FIX: Non-convergence Problem with Merge Replication =

Article ID: 239015

Article Last Modified on 3/14/2006

-

APPLIES TO


 * Microsoft SQL Server 7.0 Standard Edition

-



This article was previously published under Q239015



BUG #: 56064 (SQLBUG_70)



SYMPTOMS
Merge replication does not converge changes under the following conditions:
 * A parent/child relationship exists between two published tables without defining foreign key relationships. Instead, a join filter is used to define the relationship.

-and-
 * At the subscriber, a row is inserted that is subsequently modified after the Merge Agent is started. A typical example of this scenario would be a case where a row is inserted in the parent table and then a large number of rows are inserted into the child table, each of which is accompanied by an update to the parent table (either as a part of the same transaction or in a trigger).

Under these circumstances, Merge Agent will request a new generation for the updates and the inserts when it begins to process records. The inserts and updates that are processed after the Merge Agent begins will be converged. However, the inserts and updates that occurred before the Merge Agent started will not be converged. This results in the data not being synchronized between the publisher and the subscriber.



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.

Additional query words: merge out of sync synch sync'ed synch'ed corrupt incorrect data

Keywords: kbbug kbfix KB239015

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.