BUG: UPDLOCK Locking Option Sets Only Shared Lock with Sp_cursor

• Microsoft SQL Server version 6.5

SYMPTOMS

If 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.

WORKAROUND

To work around this problem, do either of the following:

• Use a DYNAMIC or FORWARD-ONLY cursor.

  -or-

• Use TABLOCK or HOLDLOCK instead of UPDLOCK as optional optimizer hints in the FROM clause.

STATUS

Microsoft 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.