FIX: Optimizer Hint for Index Name Fails in View

Last reviewed: April 30, 1997
Article ID: Q134823

The information in this article applies to:

Microsoft SQL Server, version 6.0

BUG# NT: 10266 (6.00)

SYMPTOMS

When you create a view using an optimizer hint to force an index and the index is specified by the index name, a query on that view fails with the following error:

   Msg 308, Level 16, State 1
   Index '%s' on table '%s' (specified in the FROM clause) does not exist.

CAUSE

Microsoft SQL Server version 6.0 incorrectly interprets the optimizer hint as an index name within a view.

WORKAROUND

In the optimizer hint, specify the index using the index id instead of the index name when you create the view. The index id can be obtained by querying the sysindexes system table.

STATUS

Microsoft has confirmed this to be a problem in Microsoft SQL Server version 6.0. This problem was corrected in Service Pack 1 for SQL Server version 6.0. For more information, contact your primary support provider.

Additional query words: query plan
Keywords : kbbug6.00 kbfix6.00.sp1 kbprg SSrvProg SSrvTran_SQL
Version : 6.0
Platform : WINDOWS
Issue type : kberrmsg

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