BUG: Query with Join in Subselect May Cause Handled Exception

Last reviewed: May 5, 1997
Article ID: Q152263

The information in this article applies to:

Microsoft SQL Server versions 6.0

BUG#: 13120

SYMPTOMS

A query with a subselect that contains a join may cause a handled exception that terminates the client connection.

WORKAROUND

Rewrite the query, possibly using a normal join instead of the subselect.

STATUS

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

MORE INFORMATION

Here is an example of a query that can cause this problem:

   SELECT A.column1
   FROM A, B
   WHERE A.id1 = B.id1  AND A.id2 = B.id2
   AND A.column1 IN (SELECT A0.column1 FROM A A0, B B0
       WHERE A0.id1 = B0.id1)

Additional query words: access violation
Keywords : kbbug6.00 kbprg SSrvProg
Version : 6.0
Platform : WINDOWS
Issue type : kbprb

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.