BUG: Insert with Union into Float Column Causes Errors

Last reviewed: April 28, 1997
Article ID: Q93554

The information in this article applies to:
  • Microsoft SQL Server version 4.2 for OS/2
BUG# OS/2: 1558 (4.2)

SYMPTOMS

An insert with union into a float (not null) column will produce the error:

   Updated or inserted row is bigger than maximum size (10 bytes)
   allowed for the table. (msg 511, level 16, state 2)"

This only happens if the float value is generated from a division involving two float values.

For example:

   insert into ck_tab
      select 1.0/1.25
      union
      select b
      from testbug

The table ck_tab is defined as:

   create table ck_tab(a float NOT NULL)

The table testbug is defined as:

   create table testbug(b float NOT NULL)

Furthermore, the problem does not occur if the float column is defined to accept NULLs.

CAUSE

SQL server does not correctly handle the maximum row size of float column in an insert into statement with union.

WORKAROUND

Change the table definition from NOT NULL to NULL.

STATUS

Microsoft has confirmed this to be a problem in SQL Server version 4.2 for OS/2. We are researching this problem and will post new information here in the Microsoft Knowledge Base as it becomes available.


Additional query words: Transact-SQL
Keywords : kbbug4.20 kbprg SSrvServer
Version : 4.2
Platform : OS/2
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 28, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.