FIX: Distribution Agent Fails with Syntax Error with Compensating Commands for Queued Updating Subscribers

This article was previously published under Q294970
This article has been archived. It is offered "as is" and will no longer be updated.
BUG #: 351300 (SHILOH)
Queued updating Subscribers is a new option in SQL Server 2000. Queued updating allows snapshot replication and transactional replication Subscribers to modify published data without requiring an active network connection to the Publisher. Because queued updating allows modifications to the same data at multiple locations, there may be conflicts when data is synchronized at the Publisher. When you create a publication by using queued updating, a conflict resolver instructs the Queue Reader Agent how to handle different versions of the same row encountered during synchronization. By default, the Publisher wins conflict resolver is set.

When the conflict resolution is set to Publisher wins.., transactional consistency is maintained based on the data at the Publisher. The conflicting transaction is rolled back at the Subscriber from which it initiated. The Queue Reader Agent detects a conflict and compensating commands are generated and propagated to the Subscriber by posting them in the distribution database. The Distribution Agent then applies the compensating commands to the Subscriber that originated the conflicting transaction. The compensating actions update the rows on the Subscriber to match the row on the Publisher.

While applying the compensating commands, the Distribution Agent encounters this error message:
Message: Line 1: Incorrect syntax near '<some sql statement>'.
The code to generate compensating commands also splits the command when it exceeds eight (8) kilobytes (KB). The way the split is performed for a string column when its value is NULL results in the creation of an extra quote. The extra quote may cause a syntax error when the compensating command is applied by the Distribution Agent.

A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem.

If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, submit a request to Microsoft Customer Service and Support to obtain the hotfix.

Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site: Note The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language. The English version of this fix should have the following file attributes or later:
   File name     -----------   s80230i.exe				
NOTE: Due to file dependencies, the most recent hotfix or feature that contains the preceding files may also contain additional files.

Microsoft has confirmed this to be a problem in SQL Server 2000.

Article ID: 294970 - Last Review: 01/16/2015 22:14:09 - Revision: 3.4

Microsoft SQL Server 2000 Standard Edition

  • kbnosurvey kbarchive kbautohotfix kbhotfixserver kbbug kbfix kbqfe kbsqlserv2000sp1fix KB294970