Microsoft KB Archive/830466

= FIX: You may receive an &quot;Internal SQL Server error&quot; error message when you run a Transact-SQL SELECT statement on a view that has many subqueries in SQL Server 2000 =

Article ID: 830466

Article Last Modified on 11/2/2007

-

APPLIES TO


 * Microsoft SQL Server 2000 Personal Edition
 * Microsoft SQL Server 2000 Developer Edition
 * Microsoft SQL Server 2000 Standard Edition
 * Microsoft SQL Server 2000 Enterprise 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 #: 470138 (SQL Server 8.0)



Microsoft distributes SQL Server 2000 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 2000 fix release.



SYMPTOMS
When you run a Transact-SQL SELECT statement on a view that has many subqueries, you may receive an error message that is similar to the following:

Server: Msg 8624, Level 16, State 21, Line 1

Internal SQL Server error.

Also, you may notice a short stack dump that is similar to the following when you start SQL Server by using the -y8624 startup option: 0087A90E Module(sqlservr+0047A90E) (CStackDump::GetContextAndDump+0000002E) 0087C41F Module(sqlservr+0047C41F) (stackTrace+00000223) 00931A0C Module(sqlservr+00531A0C) (ex_raise2+00000160) 00931CD9 Module(sqlservr+00531CD9) (ex_raisecontrol+00000080) 005F2FC2 Module(sqlservr+001F2FC2) (CSQLSource::FTransform+00000492) 0044CE55 Module(sqlservr+0004CE55) (CSQLStrings::FTransform+000001A1) 0048F6E8 Module(sqlservr+0008F6E8) (CSQLStrings::Compile+00000038) 0048F5BA Module(sqlservr+0008F5BA) (CStmtPrepQuery::CStmtPrepQuery+000002D6) 00445340 Module(sqlservr+00045340) (CCompPlan::FCompileStep+0000013E) 0044AB41 Module(sqlservr+0004AB41) (CProchdr::FCompile+00000D23) 0041BF21 Module(sqlservr+0001BF21) (CSQLSource::FTransform+0000034C) 0044CE55 Module(sqlservr+0004CE55) (CSQLStrings::FTransform+000001A1) 0041B8EF Module(sqlservr+0001B8EF) (CSQLSource::Execute+0000015B) 0048A63B Module(sqlservr+0008A63B) (language_exec+000003E1) 0042708C Module(sqlservr+0002708C) (process_commands+0000010E) 41075002 Module(UMS+00005002) (ProcessWorkRequests+00000272) 41074698 Module(UMS+00004698) (ThreadStartRoutine+00000098) 78008454 Module(MSVCRT+00008454) (endthread+000000C1) 7C4E987C Module(KERNEL32+0000987C) (SetThreadExecutionState+00000227)



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 How to obtain the latest SQL Server 2000 service pack

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 -  31-May-2003  18:45  2000.80.818.0      78,400  Console.exe 25-Jun-2003 01:01  2000.80.818.0      33,340  Dbmslpcn.dll 25-Apr-2003 02:12                    786,432  Distmdl.ldf 25-Apr-2003 02:12                  2,359,296  Distmdl.mdf 30-Jan-2003 01:55                        180  Drop_repl_hotfix.sql 23-Jun-2003 22:40  2000.80.837.0   1,557,052  Dtsui.dll 23-Jun-2003 22:40  2000.80.837.0     639,552  Dtswiz.dll 24-Apr-2003 02:51                    747,927  Instdist.sql 03-May-2003 01:56                      1,581  Inst_repl_hotfix.sql 08-Feb-2003 06:40  2000.80.765.0      90,692  Msgprox.dll 01-Apr-2003 02:07                      1,873  Odsole.sql 05-Apr-2003 01:46  2000.80.800.0      62,024  Odsole70.dll 07-May-2003 20:41  2000.80.819.0      25,144  Opends60.dll 07-May-2003 18:47                    132,096  Opends60.pdb 02-Apr-2003 21:48  2000.80.796.0      57,904  Osql.exe 02-Apr-2003 23:15  2000.80.797.0     279,104  Pfutil80.dll 04-Aug-2003 18:17                    550,780  Procsyst.sql 22-May-2003 22:57                     19,195  Qfe469571.sql 11-Jul-2003 17:04                  1,084,147  Replmerg.sql 04-Apr-2003 21:53  2000.80.798.0     221,768  Replprov.dll 08-Feb-2003 06:40  2000.80.765.0     307,784  Replrec.dll 13-Aug-2003 16:28                  1,086,797  Replsys.sql 13-Aug-2003 16:28                    986,603  Repltran.sql 29-Jul-2003 20:13  2000.80.819.0     492,096  Semobj.dll 31-May-2003 18:27  2000.80.818.0     172,032  Semobj.rll 05-Aug-2003 21:06                    127,884  Sp3_serv_uni.sql 01-Jun-2003 01:01  2000.80.818.0   4,215,360  Sqldmo.dll 07-Apr-2003 17:44                     25,172  Sqldumper.exe 19-Mar-2003 18:20  2000.80.789.0      28,672  Sqlevn70.rll 02-Jul-2003 00:18  2000.80.834.0     180,736  Sqlmap70.dll 08-Feb-2003 06:40  2000.80.765.0      57,920  Sqlrepss.dll 21-Aug-2003 21:58  2000.80.852.0   7,598,161  Sqlservr.exe 21-Aug-2003 21:58                 12,755,968  Sqlservr.pdb 25-Jul-2003 21:44  2000.80.845.0     590,396  Sqlsort.dll 08-Feb-2003 06:40  2000.80.765.0      45,644  Sqlvdi.dll 25-Jun-2003 01:01  2000.80.818.0      33,340  Ssmslpcn.dll 01-Jun-2003 01:01  2000.80.818.0      82,492  Ssnetlib.dll 01-Jun-2003 01:01  2000.80.818.0      25,148  Ssnmpn70.dll 01-Jun-2003 01:01  2000.80.818.0     158,240  Svrnetcn.dll 31-May-2003 18:59  2000.80.818.0      76,416  Svrnetcn.exe 30-Apr-2003 23:52  2000.80.816.0      45,132  Ums.dll 30-Apr-2003 23:52                    132,096  Ums.pdb 02-Jul-2003 00:19  2000.80.834.0      98,816  Xpweb70.dll Note Because of file dependencies, the most recent hotfix or feature that contains these files 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 of this article.

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

