FIX: Queries With Large Numeric Values May Not Use Appropriate Index

This article was previously published under Q262023
This article has been archived. It is offered "as is" and will no longer be updated.
BUG #: 56702 (SQLBUG_70)
Queries that use numeric values with precision 20 or greater, and scale zero, may not use the correct index. The query may use a different index, or may perform a table scan.
The optimizer converts a numeric value to a float and then gets an arithmetic overflow error, which prevents it from believing that the index is useful.
To resolve this problem, obtain U.S. Service Pack 3 for SQL Server 7.0. To activate this fix, you must enable trace flag 9256. To enable this trace flag each time that SQL Server starts, click the Startup Parameters button in the Server Properties dialog box in Enterprise Manager and add the parameter "-T9256".
Use an index hint in the query to force the use of the desired index.
Microsoft has confirmed this to be a problem in SQL Server 7.0. This problem has been corrected in U.S. Service Pack 3 for Microsoft SQL Server 7.0. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
274799 INF: How to Obtain Service Pack 3 for Microsoft SQL Server 7.0 and Microsoft Data Engine (MSDE) 1.0
For more information, contact your primary support provider.
optimizer showplan_all showplan_text showplan slow performance

Article ID: 262023 - Last Review: 10/20/2013 20:08:01 - Revision: 2.0

Microsoft SQL Server 7.0 Standard Edition

  • kbnosurvey kbarchive kbbug kbfix kbqfe KB262023