FIX: Subquery in IN Clause with DISTINCT and JOINs May Cause Access Violation

This article was previously published under Q246893
This article has been archived. It is offered "as is" and will no longer be updated.
BUG #: 56495 (SQLBUG_70)       56186 (SQLBUG_70)		
A SELECT statement causes a handled access violation (AV) exception error if all of the following conditions are true:
  • The SELECT statement contains a WHERE column IN( ) clause.
  • The IN clause contains an uncorrelated subquery.
  • The subquery uses SELECT DISTINCT.
  • The subquery contains at least two INNER JOINs.
  • The subquery contains several restrictions in the WHERE clause.
To work around this problem, replace the IN clause with an EXISTS clause, thereby correlating the subquery to the main query.
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.
sqb-query gpf gp general protection fault av

Article ID: 246893 - Last Review: 10/22/2013 03:05:08 - Revision: 2.1

  • Microsoft SQL Server 7.0 Standard Edition
  • kbnosurvey kbarchive kbbug kbfix KB246893