BUG: SELECT with More than 125 SUM Columns Can GP Fault Server

 Last reviewed: May 5, 1997
Article ID: Q103748

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

SYMPTOMS

A SELECT statement with more than 125 SUM columns of INT NULL will cause SQL Server to get a general protection fault (GP fault). 

   Example
   -------
   select sum(c2), sum(c3), sum(c4), ...  sum(c124), sum(c125), sum(c126)
   from t1
   group by c1

WORKAROUND

To avoid this problem, you can split the table into multiple tables and do a join, or you can do an inner join on the single table.

STATUS

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

Additional query words: kernel
Keywords : kbbug4.20 kbbug4.20a kbprg SSrvGPF SSrvServer SSrvWinNT
Version : 4.2a | 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: May 5, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.