SYMPTOMS
For a query of the form
SELECT ... FROM <table> WHERE (P1 AND P2) OR (P1 AND P3)
where P
n is some expression (that is, a predicate), the optimizer may fail to choose an optimal plan.
CAUSE
The SQL Server 2000 optimizer added a new feature to factor out common predicates, so that the expression shown in the "Symptoms" section is converted to the form:
P1 AND (P2 OR P3)
If there is a select index that you can use for expression P1, this factored format is easier to optimize. However, in the factored format, the optimizer fails to consider the choice of a union of two index lookups, which is an index seek on the predicate (P1 AND P2) unioned with another lookup on (P1 and P3).
RESOLUTION
A supported fix is now available from Microsoft, but it is only intended to correct the problem that is described in this article. Apply it only to computers that are experiencing this specific problem. This fix may receive additional testing. Therefore, if you are not severely affected by this problem, Microsoft recommends that you wait for the next SQL Server service pack that contains this hotfix.
To resolve this problem immediately, contact Microsoft Product Support Services to obtain the fix. For a complete list of Microsoft Product Support Services phone numbers and information about support costs, visit the following Microsoft Web site:
NOTE: In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The typical support costs will apply to additional support questions and issues that do not qualify for the specific update in question.
The English version of this fix should have the following file attributes or later:
Version File name
------------------------
8.00.262 s80262i.exe
NOTE: Due to file dependencies, the most recent hotfix or feature that contains the preceding files may also contain additional files.