FIX: Some changes may not be replicated to the subscriber correctly in SQL Server 2005 or in SQL Server 2008 when the sum of the parameters exceeds 2,100

Consider the following scenario:

• In Microsoft SQL Server 2005 or Microsoft SQL Server 2008, you set up a transactional replication.
• The transactional replication contains some articles.
• For one of the articles, you use stored procedures to deliver the insert command, the update command, and the delete command. For example, you set statement delivery to use Call <stored procedure> in the Article Properties window. Or, you specify the commands by using the @ins_cmd parameter, the @del_cmd parameter, and the @upd_cmd parameter of the sp_addarticle stored procedure.
• For another article, you use Transact-SQL commands to deliver the statements.
• You make some changes to the articles. The changes are delivered to the subscriber in the same execution batch.
• The sum of the parameters that are required to deliver the batch exceeds 2,100.
  
  Note If you use SQL Profiler Trace to capture a trace, you may find the sp_executesql stored procedure for the batch that is called by Distribution Agent.
• You synchronize the data.

In this scenario, some changes may not be replicated to the subscriber correctly.

Note You can verify that this issue occurs by using the table comparison tool (Tablediff.exe).

Additionally, the statement that occurs at the end of the batch is missed. By default, a batch contains 100 transactions.

Note You can view the replicated commands by using the sp_browsereplcmds stored procedure in the distribution database.

In this situation, if the missed statement performs an INSERT operation, a row may be missed on the subscriber. Then, if later DML operations occur on the missed row at the publisher, Distribution Agent fails, and you receive the following "error 20598" message:

Distribution Agent should detect if the 2,100 maximum parameter limit for stored procedures is exceeded. Then, Distribution Agent should move the overflowing commands to the next execution batch. However, because of a bug, the last command is skipped and is not processed.

SQL Server 2005 Service Pack 2

Important You must use this fix if you are running SQL Server 2005 Service Pack 2.

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

Note For push subscriptions, apply Cumulative Update 11 on the distribution server. For pull subscriptions, apply Cumulative Update 11 on the subscribers.

SQL Server 2005 Service Pack 3

Important You must use this fix if you are running SQL Server 2005 Service Pack 3.

The fix for this issue was also later released in Cumulative Update 1 for SQL Server 2005 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: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 2005 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:Microsoft SQL Server 2005 hotfixes are created for specific SQL Server service packs. You must apply a SQL Server 2005 Service Pack 3 hotfix to an installation of SQL Server 2005 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.

Note For push subscriptions, apply Cumulative Update 1 on the distribution server. For pull subscriptions, apply Cumulative Update 1 on the subscribers.

SQL Server 2008

The fix for this issue was first released in Cumulative Update 3. For more information about how to obtain this cumulative update package for SQL Server 2008, click the following article number to view the article in the Microsoft Knowledge Base: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. 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:Note For push subscriptions, apply Cumulative Update 3 on the distribution server. For pull subscriptions, apply Cumulative Update 3 on the subscribers.

To work around this issue, use one of the following methods.

Method 1

Decrease the value of the CommitBatchSize parameter for Distribution Agent. Therefore, you can avoid exceeding 2,100 parameters per batch of committed transactions.

Method 2

Use the same command delivery mechanism for all articles in the publication. Avoid mixing the command delivery mechanisms for articles in the same publication.

To avoid error 20598

Error 20598 may occur as a side effect of this issue. To avoid error 20598, you can use the -SkipErrors 20598 switch. After you enable this switch, Distribution Agent logs the error and then continues to process the additional rows that have to be delivered. After Distribution Agent skips error 20598, data integrity remains compromised because of the missing row. You may have to delete the row and then insert the row again at the publisher to deliver the changes to all the subscribers.

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

SQL Server 2005

For more information about what files are changed, and for information about any prerequisites to apply the cumulative update package that contains the hotfix that is described in this Microsoft Knowledge Base article, click the following article number to view the article in the Microsoft Knowledge Base:

SQL Server 2008

For more information about what files are changed, and for information about any prerequisites to apply the cumulative update package that contains the hotfix that is described in this Microsoft Knowledge Base article, click the following article number to view the article in the Microsoft Knowledge Base:

For more information about the list of builds that are available after SQL Server Service Pack 2, click the following article number to view the article in the Microsoft Knowledge Base: 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:For more information about how to obtain SQL Server 2005 Service Pack 2, click the following article number to view the article in the Microsoft Knowledge Base: For more information about the new features and the improvements in SQL Server 2005 Service Pack 2, visit the following Microsoft Web site: 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:For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base: