FIX: Floating-point Exception Generating Query Plan on Alpha

Last reviewed: December 19, 1997
Article ID: Q130981

4.21a WINDOWS kbprg kberrmsg kbbug4.21a kbfix4.21a.sp3

The information in this article applies to:

Microsoft SQL Server, version 4.21a

BUG# NT: 1781 (4.21a - NTAlpha)

SYMPTOMS

Upon executing a query including a join, with or without NOEXEC set, the following dialog box appears:

   SQLSERVR.EXE: The exception Floating-point invalid operation
   (0xc0000090) occurred in the application at location 0x00567938.
   Click on OK to terminate the application Click on CANCEL to debug
   the application.

If OK is chosen, the entire SQL Server process is terminated. This happens only on Alpha processors.

CAUSE

A floating-point underflow has occurred while the optimizer was evaluating possible join orders.

WORKAROUND

It may be possible to avoid this problem by changing the number or type of indexes available to the optimizer. The problem may disappear when there is a change in the distribution of data in the tables and UPDATE STATISTICS is run.

STATUS

Microsoft has confirmed this to be a problem in Microsoft SQL Server version 4.21a. This problem was corrected in the latest U.S. Service Pack for SQL Server version 4.21a. For information on obtaining the Service Pack, please contact your primary support provider.

Additional reference words: 4.21a Windows NT Alpha exception
KBCategory: kbprg kberrmsg kbbug4.21a kbfix4.21a.sp3
KBSubcategory: SSrvWinNT

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