BUG: Cursor Indifference to INDEX Optimizer Hints

Last reviewed: April 22, 1997
Article ID: Q165129

The information in this article applies to:

Microsoft SQL Server, versions 6.0 and 6.5

BUG# NT: 16544 (6.50)

SYMPTOMS

If a SELECT query is optimized using the optimizer hint "INDEX =", a CURSOR declared using the same SELECT and having the same optimizer hint may not optimize identically. Both performance and showplan demonstrate that the HINT index is being used in the first case, but not in the second.

WORKAROUND

To work around this problem, move relevant data into a separate table that has the desired indexing structure, and apply the cursor to it.

STATUS

Microsoft has confirmed this to be a problem in Microsoft SQL Server versions 6.0 and 6.5. We are researching this problem and will post new information here in the Microsoft Knowledge Base as it becomes available.

Keywords : kbusage SSrvGen kbbug6.00 kbbug6.50
Version : 6.0 6.5
Platform : WINDOWS
Issue type : kbbug

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