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

This article was previously published under Q293464
This article has been archived. It is offered "as is" and will no longer be updated.
BUG #: 236394 (SHILOH_BUGS)
SYMPTOMS
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.
RESOLUTION
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 theMicrosoft Knowledge Base:
290211 INF: How to Obtain the Latest SQL Server 2000 Service Pack
STATUS
Microsoft has confirmed that this is a problem in SQL Server 2000. This problem was first corrected in SQL Server 2000 Service Pack 1.
conflicts merge schema replication
Properties

Article ID: 293464 - Last Review: 01/16/2015 22:05:02 - Revision: 3.2

Microsoft SQL Server 2000 Standard Edition

  • kbnosurvey kbarchive kbbug kbfix kbsqlserv2000sp1fix KB293464
Feedback