FIX: Combination of Multiple EXIST, OR, and Subquery Clauses May Give a Sub-Optimal Plan

This article was previously published under Q294874
This article has been archived. It is offered "as is" and will no longer be updated.
BUG #: 352700 (SHILOH_BUGS)
You may see performance degradation when both of the following conditions are met:
  • OR is used on multiple EXISTS subqueries in the WHERE clause.

  • The subqueries also have EXISTS.
Under a very narrow set of circumstances that involve multiple OR, EXIST, and subquery clauses, the estimated I/O for the various steps may be incorrectly combined, which results in a sub-optimal plan choice.
To resolve this problem, obtain the latest service pack for SQL Server 2000. For additional information, click the following article number to view the article in theMicrosoft Knowledge Base:
290211 INF: How to Obtain the Latest SQL Server 2000 Service Pack
Rewrite the query to use joins rather than subqueries.
Microsoft has confirmed that this is a problem in SQL Server 2000. This problem was first corrected in SQL Server 2000 Service Pack 1.
plan optimize slow

Article ID: 294874 - Last Review: 01/16/2015 22:12:30 - Revision: 3.2

Microsoft SQL Server 2000 Standard Edition

  • kbnosurvey kbarchive kbbug kbfix kbsqlserv2000sp1fix KB294874