BUG: Convert From FLOAT to NUMERIC Causes Arithmetic Overflow

Last reviewed: April 15, 1997
Article ID: Q136532

The information in this article applies to:

Microsoft SQL Server, version 6.0

BUG# NT: 11051 (6.00) BUG# NT: 16776 (6.50)

SYMPTOMS

Explicit conversion from a FLOAT datatype to a NUMERIC datatype can cause an Arithmetic Overflow Error when any specific precision value is specified.

WORKAROUND

Use the default precision associated with the NUMERIC Datatype (18,0) instead of specifying a specific precision.

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.

Additional query words: sql6 6.00 6.50
Keywords : SSrvGen SSrvProg kbbug6.00 kbbug6.50
Version : 6.00 6.50
Platform : winnt
Issue type : kbbug
Resolution Type : No_Fix

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