BUG: Locks Held Using Optimistic Concurrency w/ No Unique Index

Last reviewed: August 19, 1997
Article ID: Q172694

The information in this article applies to:

Microsoft SQL Server, version 6.5

BUG #: 17161 (NT: 6.5)

SYMPTOMS

A dynamic or forward-only cursor opened with optimistic concurrency using either timestamps (OPTCC) or values (OPTCCVAL) will incorrectly hold a Sh_intent lock on the pages from which the rows were fetched. This problem occurs only if there is no unique index on the table.

WORKAROUND

To work around this problem, create a unique index on the table.

STATUS

Microsoft has confirmed this to be a problem in 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.

MORE INFORMATION

This problem does not occur with keyset or insensitive cursors because they default to read-only with no unique index.

Additional query words: ODBC SQL_CONCUR_ROWVER SQL_CONCUR_VALUES
Keywords : kbbug6.50 SSrvProg SSrvTran_SQL kbprg kbusage
Version : 6.5
Platform : WINDOWS
Issue type : kbbug
Solution Type : kbworkaround

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: August 19, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.