Article ID: 945896 - Last Review: December 10, 2007 - Revision: 1.1 FIX: Error message when you run a complex query in SQL Server 2005: "The query processor ran out of stack space during query optimization" Microsoft distributes Microsoft
SQL Server 2005 fixes as one downloadable file. Because the fixes are
cumulative, each new release contains all the hotfixes and all the security
fixes that were included with the previous SQL Server 2005 fix release.
SYMPTOMSWhen you compile a very complex
query on a computer that is running Microsoft SQL Server 2005 with Service Pack 2, you
may receive the following error message: Msg 8621, Level 17, State 2, Line 1 The query processor ran out of stack space during query optimization. Please simplify the query. CAUSEThe query process runs out
of stack space because of recursion during query
optimization. RESOLUTION The fix for this issue was first released in
Cumulative Update 5. For more information about how to obtain this cumulative
update package for SQL Server 2005 Service Pack 2, click the following article
number to view the article in the Microsoft Knowledge Base: 943656
(http://support.microsoft.com/kb/943656/LN/
)
Cumulative update package 5 for SQL Server 2005 Service Pack 2
Note Because the builds are cumulative, each new fix release contains
all the hotfixes and all the security fixes that were included with the
previous SQL Server 2005 fix release. Microsoft recommends that you consider
applying the most recent fix release that contains this hotfix. For more
information, click the following article number to view the article in the
Microsoft Knowledge Base: 937137
(http://support.microsoft.com/kb/937137/LN/
)
The SQL Server 2005 builds that were released after SQL Server 2005 Service Pack 2 was released
Microsoft SQL Server 2005 hotfixes are created for specific SQL
Server service packs. You must apply a SQL Server 2005 Service Pack 2 hotfix to
an installation of SQL Server 2005 Service Pack 2. By default, any hotfix that
is provided in a SQL Server service pack is included in the next SQL Server
service pack.
STATUSMicrosoft
has confirmed that this is a problem in the Microsoft products that are listed
in the "Applies to" section. REFERENCES For more
information about the list of builds that are available after SQL Server
Service Pack 2, click the following article number to view the article in the
Microsoft Knowledge Base: 937137
(http://support.microsoft.com/kb/937137/LN/
)
The SQL Server 2005 builds that were released after SQL Server 2005 Service Pack 2 was released
For more information about the Incremental Servicing Model for
SQL Server, click the following article number to view the article in the
Microsoft Knowledge Base: 935897
(http://support.microsoft.com/kb/935897/LN/
)
An Incremental Servicing Model is available from the SQL Server team to deliver hotfixes for reported problems
For more information about how to obtain SQL Server 2005 Service
Pack 2, click the following article number to view the article in the Microsoft
Knowledge Base: 913089
(http://support.microsoft.com/kb/913089/LN/
)
How to obtain the latest service pack for SQL Server 2005
For more information about the new features and the improvements
in SQL Server 2005 Service Pack 2, visit the following Microsoft Web site: http://go.microsoft.com/fwlink/?LinkId=71711
(http://go.microsoft.com/fwlink/?LinkId=71711)
For more information about the naming schema for SQL Server
updates, click the following article number to view the article in the
Microsoft Knowledge Base: 822499
(http://support.microsoft.com/kb/822499/LN/
)
New naming schema for Microsoft SQL Server software update packages
For more information about software update terminology, click the
following article number to view the article in the Microsoft Knowledge Base: 824684
(http://support.microsoft.com/kb/824684/LN/
)
Description of the standard terminology that is used to describe Microsoft software updates
APPLIES TO
| Article Translations
|
Back to the top
