You are currently offline, waiting for your internet to reconnect

FIX: Merge Agent May Ignore Subscriber-Side Changes in Articles with the Same Name

This article was previously published under Q279088
This article has been archived. It is offered "as is" and will no longer be updated.
BUG #: 57829 (SQLBUG_70)
When two separate publications are created that reference different source tables but use the same article name in both publications, the merge agent may ignore changes made at the subscriber (not replicating those changes back to the publisher).
This problem is caused by the fact that only one row is inserted into the sysmergearticles system table for the two publication articles, although there should be one entry per article in this table. The merge agent raises no error in this case, but subsequent changes in the subscriber table that does not have an entry in the sysmergearticles table are ignored.
To work around this issue, change the name of one of the publication articles. If you have already created and subscribed to the publication, you will need to unsubscribe from the publication, drop the publication, and re-create it with a different article name.
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.
replication; merge; xp_execresultset

Article ID: 279088 - Last Review: 10/21/2013 03:35:55 - Revision: 2.1

Microsoft SQL Server 7.0 Standard Edition

  • kbnosurvey kbarchive kbbug kbfix KB279088