BUG: ANSI Full Outer Join and Non-ANSI Join May Cause Handled AV

Last reviewed: February 2, 1998
Article ID: Q169346
The information in this article applies to:
  • Microsoft SQL Server, version 6.5
BUG #: 16833 (6.5)

SYMPTOMS

Optimizing a query may cause a handled access violation (AV) that stops the clients thread on the server if all of the following conditions are true:

  • The query contains the same table more than once.
  • The query does an ANSI Full Outer Join with one of the instances of the duplicated table.
  • The second instance of the table is joined to another table without the ANSI Join syntax.
  • There is no join condition between the instances of the table.

WORKAROUND

To work around this problem, rewrite the query:

  • Create a join condition between the two or more instances of the table.
  • Remove one of the instances of the table from the query.
  • Change the ANSI join to either a Left or Right Outer Join.

STATUS

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

Keywords          : kbbug6.50 SSrvGPF SSrvTran_SQL kbusage
Version           : 6.5
Platform          : WINDOWS
Issue type        : kbbug
Solution Type     : kbworkaround


================================================================================


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