FIX: Shared Table Lock Is Not Released After Lock Escalation (313302)

SYMPTOMS

When the transaction isolation level is set to READ COMMITTED, a SELECT statement that relies on prefetch and that causes a lock escalation may incorrectly hold a shared table lock on an underlying table until the end of the transaction. In this case, for a query running under the default READ COMMITTED isolation level, the expected behavior is for the shared locks to be held until the end of the statement, not the end of the transaction.

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

NOTE: The following hotfixes were created before the release of Microsoft SQL Server 2000 Service Pack 3.

The English version of this fix should have the following file attributes or later:

SQL Server 2000 Service Pack 1

This hotfix build is designed to be applied to servers running SQL Server 2000 Service Pack 1:

   Version       File name        Description
   -------------------------------------------------

   8.00.0471     Sqlservr.exe     SP1-based hotfix

SQL Server 2000 Service Pack 2

This hotfix build is designed to be applied to servers running SQL Server 2000 Service Pack 2:

   Version       File name        Description
   -------------------------------------------------

   8.00.0552     Sqlservr.exe     SP2-based hotfix

NOTE: Because of file dependencies, the most recent hotfix or feature that contains the files may also contain additional files.

FIX: Shared Table Lock Is Not Released After Lock Escalation (313302)

SYMPTOMS

RESOLUTION

STATUS