FIX: Non-convergence when a custom stored procedure propagates data changes for a transactional replication in SQL Server 2008 or in SQL Server 2008 R2

Article translations Article translations
Article ID: 2546715 - View products that this article applies to.
Microsoft distributes Microsoft SQL Server 2008 or Microsoft SQL Server 2008 R2 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 or SQL Server 2008 R2 fix release.
Expand all | Collapse all

On This Page

SYMPTOMS

Consider the following scenario:
  • You configure a transactional replication for a database in Microsoft SQL Server 2008 or in Microsoft SQL Server 2008 R2.
  • You create a custom stored procedure on the subscriber to propagate the data changes from the publisher to the subscribers.
  • The custom stored procedure contains a SELECT statement that returns a result set for an article of the publisher. This SELECT statement is located before an INSERT, UPDATE, or DELETE statement.
  • The statement after the SELECT statement encounters an error.

    For example, the custom stored procedure contains the following code:
    Create procedure [sp_ins_MyTable]
        @c1 int,
        @c2 varchar(50)
        @c3 varchar(50)
    as
    begin  
                select 1 -- In reality this would be any statement that returns a result set
                insert into Mytable( column1, column2, column3) values ( @C1, @C2, @C3)
    end  
In this scenario, non-convergence occurs in SQL Server 2008 or in SQL Server 2008 R2.

RESOLUTION

Cumulative update information

SQL Server 2008 Service Pack 3

The fix for this issue was first released in Cumulative Update 1 for SQL Server 2008 Service Pack 3. For more information about this cumulative update package, click the following article number to view the article in the Microsoft Knowledge Base:
2617146 Cumulative update package 1 for SQL Server 2008 Service Pack 3
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 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:
2629969 The SQL Server 2008 builds that were released after SQL Server 2008 Service Pack 3 was released
Microsoft SQL Server 2008 hotfixes are created for specific SQL Server service packs. You must apply a SQL Server 2008 Service Pack 3 hotfix to an installation of SQL Server 2008 Service Pack 3. By default, any hotfix that is provided in a SQL Server service pack is included in the next SQL Server service pack.

SQL Server 2008 R2

The fix for this issue was first released in Cumulative Update 9. For more information about how to obtain this cumulative update package for SQL Server 2008 R2, click the following article number to view the article in the Microsoft Knowledge Base:
2567713 Cumulative Update package 9 for SQL Server 2008 R2
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:
981356 The SQL Server 2008 R2 builds that were released after SQL Server 2008 R2 was released

SQL Server 2008 R2 Service Pack 1

The fix for this issue was first released in Cumulative Update 2 for SQL Server 2008 R2 Service Pack 1. 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:
2567714 Cumulative Update package 2 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 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 The SQL Server 2008 R2 builds that were released after SQL Server 2008 R2 Service Pack 1 was released

SQL Server 2008 SP2 CU5

The fix for this issue was first released in Cumulative Update 5. For more information about how to obtain this cumulative update package for SQL Server 2008 Service Pack 2, click the following article number to view the article in the Microsoft Knowledge Base:
2555408 Cumulative Update package 5 for SQL Server 2008 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 Service Pack 2 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:
2402659 The SQL Server 2008 builds that were released after SQL Server 2008 Service Pack 2 was released

MORE INFORMATION

For more information about how to configure the propagation of changes from the publisher to subscriber, visit the following MSDN website:

How to configure the propagation of changes from the publisher to subscriber

STATUS

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

Properties

Article ID: 2546715 - Last Review: October 18, 2011 - Revision: 3.0
APPLIES TO
  • Microsoft SQL Server 2008 Developer
  • Microsoft SQL Server 2008 Enterprise
  • Microsoft SQL Server 2008 R2 Datacenter
  • Microsoft SQL Server 2008 R2 Developer
  • Microsoft SQL Server 2008 R2 Enterprise
Keywords: 
kbqfe kbexpertiseadvanced kbsurveynew kbfix KB2546715

Give Feedback

 

Contact us for more help

Contact us for more help
Connect with Answer Desk for expert help.
Get more support from smallbusiness.support.microsoft.com