BUG: SH_PAGE Locks When Executing Sproc w/READ UNCOMMITTED

 Last reviewed: April 8, 1997
Article ID: Q153225

The information in this article applies to:
  • Microsoft SQL Server, versions 6.0 and 6.5

SYMPTOMS

If a stored procedure is executed with a reused plan in cache, SH_PAGE locks can be incorrectly acquired when using SET TRANSACTION ISOLATION LEVEL READ UNCOMMITTED. This occurs only if the reused plan in cache was originally executed without this isolation level. If the execution of the procedure requires a new plan, the problem does not occur(for example, EXEC WITH RECOMPILE).

WORKAROUND

  1. Create the procedure WITH RECOMPILE.

  2. Recompile any procedure that encounters this problem.

  3. Use the NOLOCK optimizer locking hint instead of the SET READ UNCOMMITTED option

STATUS

Microsoft has confirmed this to be a problem in Microsoft SQL Server version 6.0 and Microsoft SQL Server version 6.5. We are researching this problem and will post new information here in the Microsoft Knowledge Base as it becomes available.

Additional query words: trace flag 1200
Version : 6.0 6.5
Platform : WINDOWS

THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY.

Last reviewed: April 8, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.