FIX: AV from View with Group By and Incorrect Column List

 Last reviewed: April 9, 1997
Article ID: Q157981
The information in this article applies to:
  • Microsoft SQL Server, version 6.5
BUG#: 15978 (SQL 6.5)

SYMPTOMS

Selecting from a view which contains a correlated subquery, a group by clause, and an extra column in the views column list may cause a thread level access violation (AV) in SQL Server.

WORKAROUND

To work around this problem, do one of the following:

  • Correct the view's column list.

    -or-

  • Drop the column list.

STATUS

Microsoft has confirmed this to be a problem in Microsoft SQL Server version 6.5. This problem has been corrected in U.S. Service Pack 2 for Microsoft SQL Server version 6.5. For more information, contact your primary support provider.

MORE INFORMATION

SQL Server should not create a view which has more columns in the view's list than are created by the view's SELECT statement. SQL Server should generate the following error message: 

   Msg 4502, Level 16, State 1
   View 'XYZ' has more column names specified than columns defined.
However, if there is an extra name in the view's column list, SQL Server may create the view without generating the 4502 error. When a user then attempts to perform a SELECT against this incorrect view, he or she will generate a thread level access violation in SQL Server.

Additional query words: default
Keywords : kbbug6.50 kbfix6.50.sp2 kbusage SSrvGPF
Version : 6.5
Platform : WINDOWS

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