FIX: Columns Listed Multiple Times in GROUP BY WITH CUBE Clause Cause Access Violation

This article was previously published under Q246598
This article has been archived. It is offered "as is" and will no longer be updated.
BUG #: 53838 (SQLBUG_70)
SYMPTOMS
When the same column is listed multiple times in a GROUP BY clause that uses the CUBE operator, you may receive the following Access Violation (AV) error message:
ODBC: Msg 0, Level 19, State 1
SqlDumpExceptionHandler: Process 7 generated fatal exception c0000005 EXCEPTION_ACCESS_VIOLATION. SQL Server is terminating this process.
[Microsoft][ODBC SQL Server Driver][TCP/IP Sockets]ConnectionCheckForData ((null)()).
[Microsoft][ODBC SQL Server Driver][TCP/IP Sockets]General network error. Check your network documentation.

Connection Broken
WORKAROUND
Use table aliases and qualify the multiple instances of the column in the GROUP BY clause with the aliases.
STATUS
Microsoft has confirmed this to be a problem in SQL Server 7.0. This problem has been corrected in U.S. Service Pack 2 for Microsoft SQL Server 7.0. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
254561 INF: How to Obtain Service Pack 2 for Microsoft SQL Server 7.0 and Microsoft Data Engine (MSDE) 1.0
For more information, contact your primary support provider.
MORE INFORMATION

Steps To Reproduce The Problem

Query 1 demonstrates the problem while Query 2 uses table aliases to work around the problem.

Query 1

USE tempdbGODROP TABLE t1GOCREATE TABLE t1(c1 INT)GOSELECT c1FROM t1GROUP BY c1, c1, c1, c1WITH CUBEGO				

Query 2

USE tempdbGODROP TABLE t1goCREATE TABLE t1(c1 INT)GOSELECT a.c1FROM t1 a, t1 b, t1 c, t1 dGROUP BY a.c1, b.c1, c.c1, d.c1WITH CUBEGO				
Properties

Article ID: 246598 - Last Review: 10/22/2013 02:54:34 - Revision: 2.2

  • Microsoft SQL Server 7.0 Standard Edition
  • kbnosurvey kbarchive kbbug kbfix KB246598
Feedback