Microsoft KB Archive/933831

= FIX: A schema change that is made to a published table may not be propagated to subscriptions in SQL Server 2005 =

Article ID: 933831

Article Last Modified on 11/20/2007

-

APPLIES TO


 * Microsoft SQL Server 2005 Developer Edition
 * Microsoft SQL Server 2005 Enterprise Edition
 * Microsoft SQL Server 2005 Enterprise Edition for Itanium-based Systems
 * Microsoft SQL Server 2005 Enterprise X64 Edition
 * Microsoft SQL Server 2005 Standard Edition
 * Microsoft SQL Server 2005 Standard X64 Edition

-



SYMPTOMS
Consider the following scenario. You click Start in the View Synchronization Status window to create and then synchronize a merge replication publication in Microsoft SQL Server 2005. That is, you use this window to start a synchronization of the subscriber. Then, you run the merge agent again. In this scenario, a schema change that is made to a published table may not be propagated to subscriptions.



CAUSE
If you start a synchronization of the subscriber by using the View Synchronization Status window, the status of published articles is changed. Therefore, successive schema changes to the published articles are not propagated during synchronization.



RESOLUTION
To resolve this problem, obtain the latest service pack for Microsoft SQL Server 2005. For more information, click the following article number to view the article in the Microsoft Knowledge Base:

913089 How to obtain the latest service pack for SQL Server 2005



WORKAROUND
To work around this problem, follow these steps:
 * 1) Run the snapshot job of the publication.
 * 2) Remove and then reapply the schema change.
 * 3) Run the merge agent by using something other than the View Synchronization Status window.



STATUS
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the &quot;Applies to&quot; section. This problem was first corrected in SQL Server 2005 Service Pack 2.

Keywords: kbtshoot kbprb kbsql2005repl KB933831

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.