BUG: IN Subquery Reformats and Is Slower Than an Equivalent Join

Last reviewed: August 29, 1997
Article ID: Q173314

The information in this article applies to:

Microsoft SQL Server, versions 6.5 and 6.0

BUG #: 17227 (6.5)

SYMPTOMS

A join combined with an IN subquery may cause a reformat access plan and be much slower than the logically equivalent pure join query. In general, an IN subquery should have approximately the same performance as the equivalent join.

WORKAROUND

Express the IN subquery as join, or break it down to several smaller queries using temporary tables, which collectively produce the same result.

STATUS

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

Additional query words: sub
Keywords : kbbug6.00 kbbug6.50 SSrvGen kbusage
Version : WINDOWS:6.0 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: August 29, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.