The information in this article applies to:
BUG #: 56085 (SQLBUG_70) SYMPTOMSSQL Server 7.0 may infrequently be slower than SQL Server 6.5 when you run certain rare types of left outer joins that involve large result sets. RESOLUTIONA supported fix that corrects this problem is now available from Microsoft, but
it has not been fully regression tested and should be applied only to systems
experiencing this specific problem. If you are not severely affected by this
specific problem, Microsoft recommends that you wait for the next SQL Server service pack
that contains this fix. http://www.microsoft.com/support/supportnet/overview/overview.asp The English version of this fix should have the following file attributes or later: NOTE: Due to file dependencies, the most recent hotfix or feature that contains the above files may also contain additional files.NOTE: If this product was already installed on your computer when you purchased it from the Original Equipment Manufacturer (OEM) and you need this fix, please call the Pay Per Incident number listed on the above Web site. If you contact Microsoft to obtain this fix, and if it is determined that you only require the fix you requested, no fee will be charged. However, if you request additional technical support, and if your no-charge technical support period has expired, or if you are not eligible for standard no-charge technical support, you may be charged a non-refundable fee. For more information about eligibility for no-charge technical support, see the following article in the Microsoft Knowledge Base: Q154871 Determining If You Are Eligible for No-Charge Technical Support STATUSMicrosoft has confirmed this to be a problem in SQL Server version 7.0. MORE INFORMATION
To achieve the full benefit of this hotfix, it may be necessary to use the optimizer hint: option (loop join, force order). For more information, see SQL Server Books Online for details about using optimizer hints. It may also be necessary to make sure that clustered indexes exist on the most beneficial columns for the query. Experimentation may be required to determine the best index placement. Additional query words:
Keywords : kbSQLServ700bug |
Last Reviewed: December 14, 1999 © 2000 Microsoft Corporation. All rights reserved. Terms of Use. |