FIX: A non-convergence occurs when you run a merge replication publication that uses web synchronization if the value of a column is NULL in SQL Server 2008 R2 or in SQL Server 2012

Article ID: 2689903 - View products that this article applies to.
Microsoft distributes Microsoft SQL Server 2008 R2 or Microsoft SQL Server 2012 fixes as one downloadable file. Because the fixes are cumulative, each new release contains all the hotfixes and all the security fixes that were included with the previous SQL Server 2008 R2 fix or SQL Server 2012 release.
Expand all | Collapse all

On This Page

Symptoms

Consider the following scenario:
  • You configure a merge replication publication that uses web synchronization on an instance of Microsoft SQL Server 2008 R2 or on an instance of Microsoft SQL Server 2012.
  • An article in the publication has a table that contains a calculated column.
  • You use an update statement to update the value of a column to NULL on the subscriber. The update statement also updates multiple rows of the table.

    Note The column whose value is updated to NULL is to the right of the calculated column.

  • You run the merge replication.
In this scenario, a non-convergence occurs in which the updated data on the subscriber is not synchronized to the publisher.
Back to the top | Give Feedback

Resolution

Cumulative update information

SQL Server 2008 R2 Service Pack 2

The fix for this issue was first released in Cumulative Update 1 for SQL Server 2008 R2 Service Pack 2. For more information about how to obtain this cumulative update package, click the following article number to view the article in the Microsoft Knowledge Base:
2720425
(http://support.microsoft.com/kb/2720425/ )
Cumulative Update package 1 for SQL Server 2008 R2 Service Pack 2
Note Because the builds are cumulative, each new fix release contains all the hotfixes and all the security fixes that were included with the previous SQL Server 2008 R2 fix release. We recommend that you consider applying the most recent fix release that contains this hotfix. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
2730301
(http://support.microsoft.com/kb/2730301/ )
The SQL Server 2008 R2 builds that were released after SQL Server 2008 R2 Service Pack 2 was released

SQL Server 2012

The fix for this issue was first released in Cumulative Update 2 for SQL Server 2012. For more information about this cumulative update package, click the following article number to view the article in the Microsoft Knowledge Base:
2703275
(http://support.microsoft.com/kb/2703275/LN/ )
Cumulative update package 2 for SQL Server 2012
Note Because the builds are cumulative, each new fix release contains all the hotfixes and all the security fixes that were included with the previous SQL Server 2012 fix release. Microsoft recommends that you consider applying the most recent fix release that contains this hotfix. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
2692828
(http://support.microsoft.com/kb/2692828/LN/ )
The SQL Server 2012 builds that were released after SQL Server 2012 was released
You must apply a SQL Server 2012 hotfix to an installation of SQL Server 2012.

SQL Server 2008 R2 Service Pack 1

The fix for this issue was first released in Cumulative Update 6. For more information about how to obtain this cumulative update package for SQL Server 2008 R2 Service Pack 1, click the following article number to view the article in the Microsoft Knowledge Base:
2679367
(http://support.microsoft.com/kb/2679367/ )
Cumulative Update package 6 for SQL Server 2008 R2 Service Pack 1
Note Because the builds are cumulative, each new fix release contains all the hotfixes and all the security fixes that were included with the previous SQL Server 2008 R2 Service Pack 1 fix release. We recommend that you consider applying the most recent fix release that contains this hotfix. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
2567616
(http://support.microsoft.com/kb/2567616/ )
The SQL Server 2008 R2 builds that were released after SQL Server 2008 R2 Service Pack 1 was released
Back to the top | Give Feedback

Workaround

To work around this issue, move the calculated column to the end of the table in the article.
Back to the top | Give Feedback

Status

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
Back to the top | Give Feedback

Properties

Article ID: 2689903 - Last Review: November 19, 2012 - Revision: 6.0
Applies to
  • Microsoft SQL Server 2008 R2 Enterprise
  • Microsoft SQL Server 2008 R2 Datacenter
  • Microsoft SQL Server 2008 R2 Developer
  • Microsoft SQL Server 2008 R2 Standard
  • Microsoft SQL Server 2012 Developer
  • Microsoft SQL Server 2012 Enterprise
  • Microsoft SQL Server 2012 Standard
Keywords: 
kbtshoot kbqfe kbfix kbsurveynew kbexpertiseadvanced KB2689903
Back to the top | Give Feedback

Give Feedback

 
Back to the topBack to the top