FIX: Merge Replication Does Not Log Conflicts after Successively Adding and Dropping Columns (293464)
The information in this article applies to:
- Microsoft SQL Server 2000 (all editions)
This article was previously published under Q293464
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.
RESOLUTIONTo 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
STATUSMicrosoft has confirmed that this is a problem in SQL Server 2000. This problem was first corrected in SQL Server 2000 Service Pack 1.
| Modification Type: | Major | Last Reviewed: | 11/6/2003 |
|---|
| Keywords: | kbBug kbfix kbSQLServ2000sp1fix KB293464 |
|---|
|