FIX: Poor performance when you synchronize the data from a SQL Server 2008 R2 or a SQL Server 2012 publisher to a SQL Server compact 3.5 subscriber

Article translations Article translations
Article ID: 2616718 - 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 or SQL Server 2012 fix release.
Expand all | Collapse all

On This Page

Symptoms

Consider the following scenario:
  • You create a publisher in Microsoft SQL Server 2008 R2 or in Microsoft SQL Server 2012.
  • You create a subscriber in Microsoft SQL Server Compact 3.5.
  • You perform a merge replication to synchronize a publishing database snapshot from the publisher to the subscriber.
In this scenario, the merge replication process may experience poor performance. If you enable client-agent logging on the subscriber in SQL Server Compact 3.5, the client-side log file will show the following sequence of events for the table articles:
  • A DROP TABLE statement
  • A CREATE TABLE statement
  • One or more ALTER TABLE ADD CONSTRAINT statements for creating the default value of the rowguid column and Foreign Key constraints
  • One or more CREATE INDEX statements
  • INSERT statements for applying the initial rows to the database on the subscriber
  • Retry messages for all rows in a specific table


Notes
  • All the events in the sequence are expected results except for the retry messages. The retry messages have the following format:
    SQLCECA: mm/dd/yyyy-hh:mm:ss TblApplier::AddRetryMsg Start app=yourclientapp.exe
    SQLCECA: mm/dd/yyyy-hh:mm:ss TblApplier::AddRetryMsg add insert\update row into the retry transport. rowguid=2340e1a6-4960-e011-ac13-8000600fe800 app= yourclientapp.exe
    SQLCECA: mm/dd/yyyy-hh:mm:ss TblApplier::AddRetryMsg End hr=0 app= yourclientapp.exe
  • This issue only occurs if you perform the merge replication from a SQL Server 2008 R2 publisher to a SQL Server Compact 3.5 subscriber.

Resolution

Cumulative update information

SQL Server 2012

The fix for this issue was first released in Cumulative Update 1 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:
2679368 Cumulative update package 1 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 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 4. For more information about how to obtain this cumulative update package for SQL Server 2008 R2 SP1, click the following article number to view the article in the Microsoft Knowledge Base:
2633146 Cumulative Update package 4 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 SP1 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

Status

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

References

For more information about the Incremental Servicing Model for SQL Server, click the following article number to view the article in the Microsoft Knowledge Base:
935897 An Incremental Servicing Model is available from the SQL Server team to deliver hotfixes for reported problems
For more information about the naming schema for SQL Server updates, click the following article number to view the article in the Microsoft Knowledge Base:
822499 New naming schema for Microsoft SQL Server software update packages
For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base:
824684 Description of the standard terminology that is used to describe Microsoft software updates

Properties

Article ID: 2616718 - Last Review: November 19, 2012 - Revision: 3.0
Applies to
  • Microsoft SQL Server 2008 R2 Datacenter
  • Microsoft SQL Server 2008 R2 Enterprise
  • Microsoft SQL Server 2008 R2 Standard
  • Microsoft SQL Server 2012 Enterprise
  • Microsoft SQL Server 2012 Standard
Keywords: 
kbtshoot kbqfe kbfix kbexpertiseadvanced kbsurveynew KB2616718

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