FIX: Column Mismatch on SELECT-UNION in INSERT Causes Srv GPF

 Last reviewed: April 28, 1997
Article ID: Q100700

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

SYMPTOMS

A column mismatch in the two SELECTs making up a UNION in a SELECT-based INSERT will cause the server to general protection fault (GP-fault). This should only generate a syntax error for the user issuing the INSERT.

The following command causes the server to GP fault: 

   INSERT INTO table1
     (month_date , year_date  )
   SELECT t2.month_d, t2.year_d
   FROM table2 t2
   UNION
   SELECT t3.month_d       /* missing year_d */
   FROM table3 t3
   go
Note that this syntax error in the UNION column lists only causes of the trap if the UNION is in an INSERT statement. Running the UNION by itself generates a syntax error.

WORKAROUND

Correct the column lists and run the column again.

STATUS

Microsoft has confirmed this to be a problem in SQL Server version 4.2 for OS/2 and Windows NT. This problem was corrected in SQL Server version 6.0. For more information, contact your primary support provider.

Additional query words: insert Transact-SQL union Windows NT
Keywords : kbbug4.20 kbfix6.00 kbprg SSrvServer SSrvWinNT kbprg
Version : 4.2 | 4.2
Platform : OS/2 WINDOWS
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.