Microsoft KB Archive/312578

= FIX: Index Scans on Frequently Modified Table May Return Incorrect Results =

Article ID: 312578

Article Last Modified on 9/26/2005

-

APPLIES TO


 * Microsoft SQL Server 2000 Standard Edition

-



This article was previously published under Q312578



BUG #: 450069 (SHILOH_BUGS)



SYMPTOMS
Under rare conditions where connections concurrently modify and read data on a particular page, a query that performs a range scan on the page may return rows that do not qualify for the specified range. The end result is that a query may return extra rows that should not qualify for the query.

This problem may affect the distribution agents in transactional replication. When the Distribution Agent receives unexpected rows while querying the MSrepl_commands table it causes an access violation (AV) exception in Distrib.exe that shuts down the agent. The following text may appear in the ReplExceptDist.log: Microsoft SQL Server Replication: Exception Stack Dump ... An exception was caught in DISTRIB.EXE

Module Name Return Address Location MSVCRT 00403a45 wcsncpy + 14 distrib 0040104c 00403a45 distrib 77e97d08 0040104c KERNEL32 00000000
 * Exception Address = 7801166c
 * Exception Code = c0000005



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

290211 INF: How to Obtain the Latest SQL Server 2000 Service Pack

Hotfix
NOTE: The following hotfix was created prior to Microsoft SQL Server 2000 Service Pack 2. The English version of this fix should have the following file attributes or later:

  Version      File name        Description

8.00.468    Sqlservr.exe     SP1-based hotfix Hotfix build 468 is designed to be applied to a server that is running SQL Server 2000 Service Pack 1.

NOTE: Due to file dependencies, the most recent hotfix or feature that contains the preceding files may also contain additional files.



STATUS
Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article.

This problem was first corrected in Microsoft SQL Server 2000 Service Pack 2.

Keywords: kbbug kbfix kbqfe kbsqlserv2000presp2fix kbhotfixserver KB312578

-

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

© Microsoft Corporation. All rights reserved.