FIX: INSERT..SELECT with NOT EXISTS Can Choose Slower Merge Join Plan

This article was previously published under Q268150
This article has been archived. It is offered "as is" and will no longer be updated.
BUG #: 57872 (SQLBUG_70)
An INSERT..SELECT statement that uses a NOT EXISTS correlated subquery can choose a merge join plan that can perform more slowly than if a loop join plan is used.
Use the OPTION(LOOP JOIN) hint to force a loop join.
Microsoft has confirmed this to be a problem in SQL Server 7.0. This problem has been corrected in U.S. Service Pack 3 for Microsoft SQL Server 7.0. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
274799 INF: How to Obtain Service Pack 3 for Microsoft SQL Server 7.0 and Microsoft Data Engine (MSDE) 1.0
For more information, contact your primary support provider.

Article ID: 268150 - Last Review: 10/20/2013 23:17:44 - Revision: 2.0

Microsoft SQL Server 7.0 Standard Edition

  • kbnosurvey kbarchive kbbug kbfix kbqfe KB268150