Microsoft KB Archive/926613

= FIX: You may receive inconsistent results when you query a table that is published in a transactional replication in SQL Server 2005 =

Article ID: 926613

Article Last Modified on 11/20/2007

-

APPLIES TO


 * Microsoft SQL Server 2005 Standard Edition
 * Microsoft SQL Server 2005 Standard X64 Edition
 * Microsoft SQL Server 2005 Developer Edition
 * Microsoft SQL Server 2005 Enterprise Edition
 * Microsoft SQL Server 2005 Enterprise X64 Edition
 * Microsoft SQL Server 2005 Enterprise Edition for Itanium-based Systems

-



Bug #: 50000353 (SQL Hotfix)



Microsoft distributes Microsoft SQL Server 2005 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 2005 fix release.



SUMMARY
This article describes the following about this hotfix release:
 * The issues that are fixed by the hotfix package
 * The prerequisites for applying the hotfix package
 * Whether you must restart the computer after you apply the hotfix package
 * Whether the hotfix package replaces any other hotfix package
 * Whether you must make any registry changes after you apply the hotfix package
 * The files that are contained in the hotfix package



SYMPTOMS
Consider the following scenario. In Microsoft SQL Server 2005, you create an immediate updating pull subscription for a transactional replication. Then, you query a table that is published in the transactional replication. In this scenario, you may receive inconsistent results. For example, data that was deleted in a previous transaction may be returned.

Additionally, transactional replication may fail, and you may receive error messages that resemble the following:

Message 1

Msg 20515, Level 16, State 1, Procedure sp_MSreplraiserror, Line 9

Updateable Subscriptions: Rows do not match between Publisher and Subscriber.

Run the Distribution Agent to refresh rows at the Subscriber.

Message 2

Msg 20512, Level 16, State 1, Procedure sp_MSreplraiserror, Line 8

Updateable Subscriptions: Rolling back transaction.

Message 3

Msg 3609, Level 16, State 1, Line 5

The transaction ended in the trigger. The batch has been aborted.



CAUSE
Whether this issue occurs depends on the timing of the agents that you are running. This issue occurs in SQL Server 2005 because of changes that are have been made in the loopback detection. These changes enable republishing of immediate updating replication scenarios. The changes propagate commands that are initiated from a Subscriber back to that Subscriber. The changes rely on Subscriber-side custom stored procedures to filter out duplicates.

This issue occurs in the following scenario:
 * You insert a row at a Subscriber.
 * You run the Logreader.exe file at the publisher. Then, the Publisher runs the INSERT command.
 * You delete this row at the Subscriber.
 * You run the Distribution Agent from the Publisher to the Subscriber.

The Distribution Agent will deliver the row that you inserted back to the Subscriber. This behavior occurs although the insertion was initiated by the Subscriber and although the row no longer exists on the Subscriber. When you run the Logreader.exe file later, the Distribution Agent delivers the DELETE command to the Subscriber. At this point, the Publisher and the Subscriber become synchronized again.



Service pack information
To resolve this problem, obtain the latest service pack for SQL Server 2005. For more information, click the following article number to view the article in the Microsoft Knowledge Base:

913089 How to obtain the latest service pack for SQL Server 2005

Hotfix information
A supported hotfix is now available from Microsoft. However, it is intended to correct only the problem that is described in this article. Apply it only to systems that are experiencing this specific problem. This hotfix may receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next Microsoft SQL Server 2005 service pack that contains this hotfix.

To resolve this problem immediately, contact Microsoft Customer Support Services to obtain the hotfix. For a complete list of Microsoft Customer Support Services telephone numbers and information about support costs, visit the following Microsoft Web site:

http://support.microsoft.com/contactus/?ws=support

Note In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The usual support costs will apply to additional support questions and issues that do not qualify for the specific update in question.

Prerequisites
To apply this hotfix, you must have SQL Server 2005 Service Pack 1 (SP1) installed. For more information about SQL Server 2005 service packs, click the following article number to view the article in the Microsoft Knowledge Base:

913089 How to obtain the latest service pack for SQL Server 2005

Restart information
You do not have to restart the computer after you apply this hotfix.

Hotfix replacement information
This hotfix does not replace any other hotfixes.

Registry information
You do not have to change the registry after you apply this hotfix.

File information
This hotfix contains only those files that are required to correct the issues that are listed in this article. This hotfix may not contain all the files that you must have to fully update a product to the latest build.

The English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.

Microsoft SQL Server 2005, Itanium architecture version


STATUS
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the &quot;Applies to&quot; section. This problem was first corrected in SQL Server 2005 Service Pack 2.



MORE INFORMATION
For more information about the naming schema for Microsoft 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

Keywords: kbbug kbfix kbqfe atdownload kbsql2005engine kbsql2005sp2fix KB926613

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.