The information in this article applies to:
BUG #: 53342 (SQLBUG_70) SYMPTOMS
Positioned updates on a cursor may experience non-linear performance
degradation as the number of rows affected by the cursor increases. This
will occur either if the cursor is opened using ANSI syntax and updated
using the WHERE CURRENT OF syntax, or if the cursor is opened and updated
through an application making DB-Library, ODBC, or OLE DB calls. WORKAROUNDTo work around this problem, create a primary key or unique index on the table. Performance should scale roughly linearly with the number of rows affected by the cursor. STATUSMicrosoft has confirmed this to be a problem in SQL Server version 7.0. MORE INFORMATION
The primary key or unique index described in the WORKAROUND section of this
article does not need to be (although it may be) on any of the columns the
cursor is opened on or the column(s) being updated. Any column(s) that will
uniquely identify each row is a valid choice for a primary key or unique
index.
Additional query words:
PK hang slows down sp_cursoropen sp_cursor oledb lib
Keywords : kbbug7.00 |
Last Reviewed: April 19, 1999 © 2000 Microsoft Corporation. All rights reserved. Terms of Use. |