FIX: Internal Query Processor Error 8623 When Microsoft SQL Server Tries to Compile a Plan for a Complex Query

View products that this article applies to.

SYMPTOMS

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

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

This error is not based on any particular query construct. Also, this error is not limited to any particular database environment, to any particular amount of data, or to any particular kind of data. This error may first occur only sporadically. However, this error may occur repeatedly after the first time it occurs.

Back to the top

RESOLUTION

Service pack information

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 hotfix 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
   --------------------------------------------------------------
   25-Feb-2003  18:41  2000.80.777.0      29,244  Dbmslpcn.dll     
   07-Feb-2003  20:44                    786,432  Distmdl.ldf
   07-Feb-2003  20:44                  2,359,296  Distmdl.mdf
   29-Jan-2003  16:55                        180  Drop_repl_hotfix.sql
   07-Apr-2003  10:15  2000.80.801.0   1,557,052  Dtsui.dll        
   29-Jan-2003  20:18                    746,470  Instdist.sql
   29-Jan-2003  16:55                      1,402  Inst_repl_hotfix.sql
   07-Feb-2003  21:40  2000.80.765.0      90,692  Msgprox.dll      
   31-Mar-2003  17:07                      1,873  Odsole.sql
   04-Apr-2003  16:46  2000.80.800.0      62,024  Odsole70.dll     
   02-Apr-2003  12:48  2000.80.796.0      57,904  Osql.exe         
   02-Apr-2003  14:15  2000.80.797.0     279,104  Pfutil80.dll     
   04-Apr-2003  12:27                  1,083,467  Replmerg.sql
   04-Apr-2003  12:53  2000.80.798.0     221,768  Replprov.dll     
   07-Feb-2003  21:40  2000.80.765.0     307,784  Replrec.dll      
   31-Mar-2003  17:23                  1,084,828  Replsys.sql
   03-Apr-2003  09:14                    104,868  Sp3_serv_uni.sql
   07-Apr-2003  08:44                     25,172  Sqldumper.exe    
   19-Mar-2003  09:20  2000.80.789.0      28,672  Sqlevn70.rll
   27-Feb-2003  16:34  2000.80.778.0     176,696  Sqlmap70.dll     
   07-Feb-2003  21:40  2000.80.765.0      57,920  Sqlrepss.dll     
   11-Apr-2003  13:52  2000.80.804.0   7,540,817  Sqlservr.exe     
   07-Feb-2003  21:40  2000.80.765.0      45,644  Sqlvdi.dll       
   25-Feb-2003  18:41  2000.80.777.0      29,244  Ssmslpcn.dll     
   25-Feb-2003  18:41  2000.80.777.0      82,492  Ssnetlib.dll     
   17-Mar-2003  05:49                    727,132  Sysmessages.sym
   27-Feb-2003  16:34  2000.80.778.0      98,872  Xpweb70.dll

Note Because of file dependencies, the most current hotfix or the most current feature that contains the files in this table 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 at the beginning of this article. This problem was first corrected in Microsoft SQL Server 2000 Service Pack 4.

Back to the top