FIX: Five-way Table Join w/OR May Cause Handled Exception

Last reviewed: April 8, 1997
Article ID: Q152264

The information in this article applies to:

Microsoft SQL Server versions 6.0 and 6.5

SYMPTOMS

A five-way (or more) table join with a search clause introduced by an OR clause may cause handled exception which terminates the client thread.

WORKAROUND

Rewrite the query such that the rows not in the join qualify for the query because of the OR clause.

STATUS

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

MORE INFORMATION

Here is an example of the type of query that would cause this problem:

   SELECT * FROM A, B, C, D, E
   WHERE A.id = B.id AND B.bid = C.bid AND C.cid = D.cid AND D.did = E.did
   OR A.column1 = "test"

Additional query words: multiple access violation
Keywords : kbbug6.00 kbbug6.50 kbfix6.00.sp3 kbfix6.50.sp1 kbprg SSrvProg
Version : 6.0 6.5
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: April 8, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.