The information in this article applies to:
BUG #: 16301 (SQLBUG_65) SYMPTOMS
A query can be very slow if the qualifying column used in the where clause
is either a numeric or decimal data type. The query can be slow even if the
columns have indexes. A show plan of the query shows that the optimizer
chooses to do a table scan rather than use the index.
WORKAROUNDChange your query to use another column as the qualifier, or use a composite index with the first part of the index key not being a decimal or numeric data type. Another workaround is to change the qualifying column used in the where clause to truly be numeric or decimal. For example, instead of using 9, use 9.0, or do a convert to numeric or decimal. STATUSMicrosoft has confirmed this to be a problem in SQL Server
version 6.5. This problem has been corrected in U.S. Service Pack 5a
for Microsoft SQL Server version 6.5. For information about
downloading and installing the latest SQL Server Service Pack, see
http://support.microsoft.com/support/sql/.
Additional query words:
Keywords : kbusage SSrvGen kbbug6.50.sp2 |
Last Reviewed: November 17, 1999 © 2000 Microsoft Corporation. All rights reserved. Terms of Use. |