The information in this article applies to:
BUG#: 14238 (6.00) SYMPTOMS
If a stored procedure is executed after setting the TRANSACTION ISOLATION
LEVEL to READ UNCOMMITTED, the procedure can fail with the following error:
CAUSE
This problem occurs if a stored procedure plan is reused in cache that was
compiled when the user was not using READ UNCOMMITTED. If a new plan is
used to execute the procedure with READ UNCOMMITTED, the problem does not
occur.
WORKAROUND
Use the locking hint keyword NOLOCK in the SELECT statement instead of SET
TRANSACTION ISOLATION LEVEL READ UNCOMMITTED.
STATUS
Microsoft has confirmed this to be a problem in Microsoft SQL Server
version 6.0. We are researching this problem and will post new information
here in the Microsoft Knowledge Base as it becomes available.
Additional query words: sql6 sproc sp
Keywords : kbprg SSrvStProc kbbug6.00 |
Last Reviewed: March 25, 1999 © 2000 Microsoft Corporation. All rights reserved. Terms of Use. |