Article ID: 816440 - Last Review: November 2, 2007 - Revision: 5.3

FIX: Error 8623 is Raised When SQL Server Compiles a Complex Query

View products that this article applies to.

System TipThis article applies to a different operating system than the one you are using. Article content that may not be relevant to you is disabled.

BUG #: 364311 (SHILOH_BUGS)
BUG #: 364285 (SHILOH_BUGS)

SYMPTOMS

When SQL Server tries to compile a plan for a complex query, you might receive the following error message:

Server: Msg 8623, Level 16, State 1, Line 1 Internal Query Processor Error:
The query processor could not produce a query plan. Contact your primary support provider for more information.

The error is not based on any particular query construct, and it is not limited to any particular database environment, or statistics distribution.

Back to the top

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 (http://support.microsoft.com/kb/290211/ ) How to obtain the latest SQL Server 2000 service pack

Back to the top

Hotfix information

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
   ---------------------------------------------------------------------------
   26-Feb-2003  03:41  2000.80.777.0      29,244 bytes  Dbmslpcn.dll     
   08-Feb-2003  05:43                    786,432 bytes  Distmdl.ldf
   08-Feb-2003  05:43                  2,359,296 bytes  Distmdl.mdf
   30-Jan-2003  01:55                        180 bytes  Drop_repl_hotfix.sql
   01-Feb-2003  00:32  2000.80.763.0   1,557,052 bytes  Dtsui.dll        
   30-Jan-2003  05:18                    746,470 bytes  Instdist.sql
   30-Jan-2003  01:55                      1,402 bytes  Inst_repl_hotfix.sql
   08-Feb-2003  06:40  2000.80.765.0      90,692 bytes  Msgprox.dll
   26-Mar-2003  01:43                  1,066,588 bytes  Replmerg.sql
   08-Feb-2003  06:40  2000.80.765.0     221,768 bytes  Replprov.dll
   08-Feb-2003  06:40  2000.80.765.0     307,784 bytes  Replrec.dll      
   07-Mar-2003  05:02                  1,084,369 bytes  Replsys.sql
   03-Mar-2003  17:18                    104,958 bytes  Sp3_serv_uni.sql
   19-Mar-2003  18:20  2000.80.789.0      28,672 bytes  Sqlevn70.rll
   28-Feb-2003  01:34  2000.80.778.0     176,696 bytes  Sqlmap70.dll
   08-Feb-2003  06:40  2000.80.765.0      57,920 bytes  Sqlrepss.dll
   02-Apr-2003  18:42  2000.80.794.0   7,540,820 bytes  Sqlservr.exe
   08-Feb-2003  06:40  2000.80.765.0      45,644 bytes  Sqlvdi.dll
   26-Feb-2003  03:41  2000.80.777.0      29,244 bytes  Ssmslpcn.dll
   26-Feb-2003  03:41  2000.80.777.0      82,492 bytes  Ssnetlib.dll
   17-Mar-2003  14:49                    727,132 bytes  Sysmessages.sym
   28-Feb-2003  01:34  2000.80.778.0      98,872 bytes  Xpweb70.dll

Note Because of file dependencies, the most recent hotfix or feature that contains the files may also contain additional files.

Back to the top

STATUS

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.This problem was first corrected in Microsoft SQL Server 2000 Service Pack 4.

Back to the top