KB2616718 - 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

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

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 problemsFor 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 packagesFor 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