FIX: Updates to New Column Added to Merge Publication Article Are Not Replicated (290369)



The information in this article applies to:

  • Microsoft SQL Server 2000 Developer Edition
  • Microsoft SQL Server 2000 Enterprise Edition
  • Microsoft SQL Server 2000 Enterprise Evaluation Edition
  • Microsoft SQL Server 2000 Personal Edition
  • Microsoft SQL Server 2000 Standard Edition

This article was previously published under Q290369
BUG #: 235348 (SHILOH_BUGS)

SYMPTOMS

Updates to a table used in a merge publication may not replicate if all the following conditions are met:

  • The table is used in a merge publication and the initial snapshot has been applied at the Subscriber.
  • The Merge Agent is running in Continuous mode.
  • Rows have been replicated between the Publisher and the Subscriber.
  • A new column is added to the table on the Publisher by using the sp_repladdcolumn stored procedure.
  • After the new column has been replicated to the Subscriber, update the new column on the Publisher.
After the new column is updated on the Publisher, the next time the Merge Agent runs it indicates that updates have occurred. However, if you query the table on the Subscriber, the updates to the new column are not reflected.

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 the Microsoft Knowledge Base:

290211 INF: How to Obtain the Latest SQL Server 2000 Service Pack

WORKAROUND

Unsubscribe to the publication before you add the new column on the Publisher. After the new column is added, subscribe to the publication again and reinitialize.

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.

MORE INFORMATION

Stopping and restarting the Merge Agent does not resolve this problem.

Modification Type:MajorLast Reviewed:6/25/2004
Keywords:kbBug kbfix kbSQLServ2000sp1fix KB290369