SYMPTOMS
When SQL Server runs a parameterized query that contains
several IN clauses, each with a large number of values, SQL Server may return
the following error message after a minute or more of high CPU utilization:
Server: Msg 8623, Level 16, State 1
Internal Query
Processor Error: The query processor could not produce a query plan. Contact
your primary support provider for more information.
If you receive
error message 7399, but your circumstances do not match the symptoms in this
article, search the Microsoft Knowledge Base for other potential causes of this
error message.
RESOLUTION
To resolve this problem, obtain the latest
service pack for Microsoft SQL Server 2000. For additional information, click
the following article number to view the article in the Microsoft Knowledge
Base:
290211 INF: How To Obtain the Latest SQL Server 2000 Service Pack
: The following hotfix was created before the release of Microsoft
SQL Server 2000 Service Pack 3.
The English version of this fix has
the file attributes (or later) that are listed in the following table. The
dates and times for these files are listed in coordinated universal time (UTC).
When you view the file information, it is converted to local time. To find the
difference between UTC and local time, use the
Time Zone tab in the Date and Time tool in Control Panel.
Date Time Version Size File name
----------------------------------------------------------------------
06/25/2002 01:40 PM 2000.80.648.0 7,454,801 bytes Sqlservr.exe
NOTE: Because of file dependencies, the most recent hotfix or feature
that contains the files may also contain additional
files.
Note that this fix works only when you
use trace flag 9268. The activation of trace flag 9268 changes the way the
optimizer evaluates each IN clause in the query resulting in the generation of
a viable query plan.
For more information about the use of trace
flags, see the "trace flags" topic in SQL Server 2000 Books Online. The meaning
of trace flag 9268 may change in the next major product version, or its use may
be unsupported. Only use trace flag 9268 on systems that experience this
problem. You must review the use of the trace flag before any major version
upgrade.