BUG: UPDLOCK Locking Option Sets Only Shared Lock with Sp_cursorLast reviewed: March 6, 1998Article ID: Q179222 |
The information in this article applies to:
SYMPTOMSIf you open a KEYSET cursor with the locking option UPDLOCK through sp_cursoropen in a transaction, only a shared lock is set on the pages with the qualifying data rows. With the first sp_cursorfetch, an Update_page lock is set. This leads to a good chance to run into a deadlock.
WORKAROUNDTo work around this problem, do either of the following:
STATUSMicrosoft has confirmed this to be a problem in SQL Server version 6.5. A supported fix is now available, but has not been fully regression- tested and should be applied only to systems experiencing this specific problem. Unless you are severely impacted by this specific problem, Microsoft recommends that you wait for the next Service Pack that contains this fix. Contact Microsoft Technical Support for more information.
|
Additional query words: blocking
© 1998 Microsoft Corporation. All rights reserved. Terms of Use. |