BUG: SH_PAGE Locks When Executing Sproc w/READ UNCOMMITTED (153225)


The information in this article applies to:

  • Microsoft SQL Server 6.0
  • Microsoft SQL Server 6.5
This article was previously published under Q153225

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.
Modification Type:MinorLast Reviewed:3/1/2005
Keywords:kbBug KB153225
©2004 Microsoft Corporation. All rights reserved.