FIX: Merge Replication Does Not Log Conflicts after Successively Adding and Dropping Columns

Article translations Article translations
Article ID: 293464 - View products that this article applies to.
This article was previously published under Q293464
BUG #: 236394 (SHILOH_BUGS)
Expand all | Collapse all


SQL Server 2000 supports schema changes to articles in an existing publication. When a column is added and dropped from an article published for Merge replication, conflicts might not be logged for successive generations.


To resolve this problem, obtain the latest service pack for SQL Server 2000. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:
290211 INF: How to Obtain the Latest SQL Server 2000 Service Pack


Microsoft has confirmed that this is a problem in SQL Server 2000. This problem was first corrected in SQL Server 2000 Service Pack 1.


Article ID: 293464 - Last Review: November 6, 2003 - Revision: 3.2
  • Microsoft SQL Server 2000 Standard Edition
kbbug kbfix kbsqlserv2000sp1fix KB293464

Give Feedback


Contact us for more help

Contact us for more help
Connect with Answer Desk for expert help.
Get more support from