Microsoft KB Archive/843263

= FIX: You may receive an 8623 error message when you try to run a complex query on an instance of SQL Server =

Article ID: 843263

Article Last Modified on 11/2/2007

-

APPLIES TO


 * Microsoft SQL Server 2000 Developer Edition
 * Microsoft SQL Server 2000 Standard Edition
 * Microsoft SQL Server 2000 Enterprise Edition
 * Microsoft SQL Server 2000 Personal Edition
 * Microsoft SQL Server 2000 Enterprise Edition
 * Microsoft SQL Server 2000 Workgroup Edition
 * Microsoft SQL Server 2000 Desktop Engine (Windows)
 * Microsoft SQL Server 2000 Developer Edition
 * Microsoft SQL Server 2000 Enterprise Edition 64-bit

-



Bug #: 471546 (SQL Server 8.0)

Bug #: 23602 (Content Maintenance)



Microsoft SQL Server 2000 fixes are distributed 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 2000 fix release.



SYMPTOMS
When you try to compile and run certain queries, the SQL Server optimizer may occasionally return 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.

Note This problem is not limited to any particular query construct, database environment, or statistics distribution. The error message is based on certain costing inconsistencies that occur when the SQL Server optimizer calculates the cost that is associated with various possible query plans for the query.



Service pack information
To resolve this problem, obtain the latest service pack for Microsoft SQL Server 2000. For more information, click the following article number to view the article in the Microsoft Knowledge Base:

290211 How to obtain the latest SQL Server 2000 service pack

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 03-Jun-2004 14:24  2000.80.948.0     664,128  Autoplt.dll 03-Jun-2004 14:53  2000.80.948.0      78,400  Console.exe 03-Jun-2004 15:13  2000.80.948.0     315,968  Custtask.dll 03-Jun-2004 14:26  2000.80.948.0      33,340  Dbmslpcn.dll 08-Apr-2004 09:12                    786,432  Distmdl.ldf 08-Apr-2004 09:12                  2,359,296  Distmdl.mdf 10-Oct-2003 06:18                        180  Drop_repl_hotfix.sql 03-Jun-2004 15:10  2000.80.948.0   1,905,216  Dtspkg.dll 03-Jun-2004 15:23  2000.80.948.0     528,960  Dtspump.dll 03-Jun-2004 15:27  2000.80.948.0   1,557,052  Dtsui.dll 03-Jun-2004 15:30  2000.80.948.0     639,552  Dtswiz.dll 10-Oct-2003 06:18                    747,927  Instdist.sql 10-Oct-2003 06:18                      1,581  Inst_repl_hotfix.sql 03-Jun-2004 15:40  2000.80.948.0     352,828  Isqlw.exe 03-Jun-2004 15:33  2000.80.948.0      82,492  Itwiz.exe 03-Jun-2004 14:26  2000.80.948.0      90,692  Msgprox.dll 19-May-2004 11:13  8.11.40209.0      209,408  Mssdi98.dll 03-Jun-2004 14:29  2000.80.948.0      62,024  Odsole70.dll 03-Jun-2004 15:37  2000.80.948.0      25,144  Opends60.dll 03-Jun-2004 14:29  2000.80.948.0      57,904  Osql.exe 03-Jun-2004 15:15  2000.80.948.0     279,104  Pfutil80.dll 10-Oct-2003 06:07                    550,780  Procsyst.sql 08-Apr-2004 09:12                     12,305  Qfe469315.sql 08-Apr-2004 09:12                     19,195  Qfe469571.sql 03-Jun-2004 16:27                  1,104,848  Replmerg.sql 03-Jun-2004 14:38  2000.80.948.0     221,768  Replprov.dll 03-Jun-2004 14:39  2000.80.948.0     307,784  Replrec.dll 03-Jun-2004 14:29  2000.80.948.0     159,813  Replres.rll 10-Oct-2003 06:18                  1,087,150  Replsys.sql 10-Oct-2003 06:18                    986,603  Repltran.sql 03-Jun-2004 14:43  2000.80.948.0     287,304  Rinitcom.dll 03-Jun-2004 14:26  2000.80.948.0      78,416  Sdiclnt.dll 03-Jun-2004 14:09  2000.80.948.0      66,112  Semmap.dll 03-Jun-2004 14:13  2000.80.948.0      57,916  Semnt.dll 03-Jun-2004 15:19  2000.80.948.0     492,096  Semobj.dll 03-Jun-2004 15:14  2000.80.948.0     172,032  Semobj.rll 03-Jun-2004 14:43  2000.80.948.0      53,832  Snapshot.exe 11-Mar-2004 14:40                    117,834  Sp3_serv_uni.sql 03-Jun-2004 14:14  2000.80.948.0      28,672  Sqlagent.dll 03-Jun-2004 14:18  2000.80.948.0     311,872  Sqlagent.exe 03-Jun-2004 14:40  2000.80.948.0     168,001  Sqlakw32.dll 03-Jun-2004 14:23  2000.80.948.0      33,344  Sqlctr80.dll 03-Jun-2004 15:34  2000.80.948.0   4,215,360  Sqldmo.dll 03-Jun-2004 14:45                     25,172  Sqldumper.exe 03-Jun-2004 14:19  2000.80.948.0      28,672  Sqlevn70.rll 03-Jun-2004 14:51  2000.80.948.0     180,792  Sqlmap70.dll 03-Jun-2004 15:31  2000.80.948.0     188,992  Sqlmmc.dll 03-Jun-2004 15:28  2000.80.948.0     479,232  Sqlmmc.rll 03-Jun-2004 15:19  2000.80.948.0     401,984  Sqlqry.dll 03-Jun-2004 14:46  2000.80.948.0      57,920  Sqlrepss.dll 03-Jun-2004 14:23  2000.80.948.0   7,512,640  Sqlservr.exe 03-Jun-2004 14:13  2000.80.948.0     590,396  Sqlsort.dll 03-Jun-2004 14:46  2000.80.948.0      45,644  Sqlvdi.dll 03-Jun-2004 14:47  2000.80.948.0     106,588  Sqsrvres.dll 03-Jun-2004 14:26  2000.80.948.0      33,340  Ssmslpcn.dll 03-Jun-2004 14:29  2000.80.948.0      82,492  Ssnetlib.dll 03-Jun-2004 15:01  2000.80.948.0      25,148  Ssnmpn70.dll 03-Jun-2004 14:49  2000.80.948.0     123,456  Stardds.dll 03-Jun-2004 14:50  2000.80.948.0     158,240  Svrnetcn.dll 03-Jun-2004 14:50  2000.80.948.0      76,416  Svrnetcn.exe 03-Jun-2004 14:58  2000.80.948.0      53,808  Ums.dll 03-Jun-2004 14:50  2000.80.948.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.



STATUS
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the &quot;Applies to&quot; section.

This problem was first corrected in Microsoft SQL Server 2000 Service Pack 4.

