Help and Support

FIX: Error message when you run an UPDATE statement that uses two JOIN hints to update a table in SQL Server 2000: "Internal SQL Server error"

View products that this article applies to.
Article ID:902852
Last Review:November 2, 2007
Revision:1.2
Bug #: 474596 (SQL Server 8.0)
Bug #: 474470 (SQL Server 8.0)
Microsoft distributes Microsoft 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.
On This Page

SUMMARY

This article describes the following about this hotfix release:
•The issues that are fixed by this hotfix package
•The prerequisites for installing the hotfix package
•Information about whether you must restart the computer after you install the hotfix package
•Information about whether the hotfix package is replaced by any other hotfix package
•Information about whether you must make any registry changes
•The files that are contained in the hotfix package

Back to the top

SYMPTOMS

Consider the following scenario. In Microsoft SQL Server 2000, you try to update a table by running an UPDATE statement. The UPDATE statement joins three tables by using two JOIN hints. In this scenario, you receive the following error message:
Server: Msg 8624, Level 16, State 1, Line 1
Internal SQL Server error.
Because of the nature of this error message, we strongly recommend that you contact Microsoft Product Support Services to analyze your symptoms and determine whether you are running into this problem.

For a list of all publicly released SQL Server 2000 Post-Service Pack 3a hotfixes, see the following article in the Microsoft Knowledge Base:
810185 (http://support.microsoft.com/kb/810185/) SQL Server 2000 hotfix update for SQL Server 2000 Service Pack 3 and 3a

Back to the top

CAUSE

This problem occurs because of an incorrect evaluation in the optimization phase of the query.

Back to the top

RESOLUTION

Hotfix information

A supported hotfix is now available from Microsoft, but it is only intended to correct the problem that is described in this article. Only apply it to systems that are experiencing this specific problem. This hotfix may receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next Microsoft SQL Server 2000 service pack that contains this hotfix.

To resolve this problem immediately, contact Microsoft Product Support Services to obtain the hotfix. For a complete list of Microsoft Product Support Services telephone numbers and information about support costs, visit the following Microsoft Web site:
http://support.microsoft.com/contactus/?ws=support (http://support.microsoft.com/contactus/?ws=support)
Note In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The usual support costs will apply to additional support questions and issues that do not qualify for the specific update in question.

Prerequisites

You must have Microsoft SQL Server 2000 Service Pack 3 (SP3) and baseline 8.00.1007 installed to apply this hotfix.

For more information about how to obtain SQL Server 2000 Service Pack 3, 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

Restart information

You do not have to restart the computer after you apply this hotfix.

Registry information

You do not have to change the registry after you apply this hotfix.

Hotfix file information

This hotfix contains only those files that are required to correct the issues that this article lists. This hotfix may not contain of all the files that you must have to fully update a product to the latest build.

The English version of this hotfix has the file attributes (or later file attributes) 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.
SQL Server 2000 32-bit versions
File nameFile versionFile sizeDateTimePlatform
Autoplt.dll2000.80.1029.0664,12821-Jun-200511:07x86
Console.exe2000.80.1029.078,40021-Jun-200511:07x86
Ctasksui.dll2000.80.1029.0332,35221-Jun-200511:07x86
Custtask.dll2000.80.1029.0315,96821-Jun-200511:07x86
Dbmslpcn.dll2000.80.1029.033,34021-Jun-200511:07x86
Distmdl.ldfNot Applicable786,43214-Apr-200510:17Not Applicable
Distmdl.mdfNot Applicable2,359,29614-Apr-200510:17Not Applicable
Drop_repl_hotfix.sqlNot Applicable18014-Apr-200510:17Not Applicable
Dtspkg.dll2000.80.1029.01,905,21621-Jun-200511:07x86
Dtspump.dll2000.80.1029.0528,96021-Jun-200511:07x86
Dtsui.dll2000.80.1029.01,557,05221-Jun-200511:07x86
Dtswiz.dll2000.80.1029.0639,55221-Jun-200511:07x86
Impprov.dll2000.80.1029.0102,99221-Jun-200511:07x86
Instdist.sqlNot Applicable747,92714-Apr-200510:17Not Applicable
Inst_repl_hotfix.sqlNot Applicable1,58114-Apr-200510:17Not Applicable
Isqlw.exe2000.80.1029.0352,82821-Jun-200511:07x86
Itwiz.exe2000.80.1029.082,49221-Jun-200511:07x86
Msgprox.dll2000.80.1029.090,69221-Jun-200511:07x86
Mssdi98.dll8.11.41022.0226,30414-Apr-200509:59x86
Odsole70.dll2000.80.1029.062,02421-Jun-200511:07x86
Opends60.dll2000.80.1029.025,14421-Jun-200511:08x86
Osql.exe2000.80.1029.057,90421-Jun-200511:07x86
Pfutil80.dll2000.80.1029.0279,10421-Jun-200511:07x86
Procsyst.sqlNot Applicable551,01214-Apr-200510:13Not Applicable
Qfe469315.sqlNot Applicable12,30514-Apr-200510:17Not Applicable
Qfe469571.sqlNot Applicable19,19514-Apr-200510:17Not Applicable
Qfe472197.sqlNot Applicable5,15714-Apr-200510:17Not Applicable
Qrdrsvc.exe2000.80.1029.0143,94021-Jun-200511:07x86
Replmerg.sqlNot Applicable1,136,16021-Jun-200510:54Not Applicable
Replprov.dll2000.80.1029.0221,76821-Jun-200511:07x86
Replrec.dll2000.80.1029.0307,78421-Jun-200511:07x86
Replres.rll2000.80.1029.0159,81317-Jun-200507:42Not Applicable
Replsys.sqlNot Applicable1,088,24014-Apr-200510:17Not Applicable
Repltran.sqlNot Applicable986,74614-Apr-200510:17Not Applicable
Repl_uninstall.sqlNot Applicable5514-Apr-200510:17Not Applicable
Rinitcom.dll2000.80.1029.0287,30421-Jun-200511:07x86
Sdiclnt.dll2000.80.1029.078,41621-Jun-200511:07x86
Semexec.dll2000.80.1029.0823,87221-Jun-200511:07x86
Semmap.dll2000.80.1029.066,11221-Jun-200511:07x86
Semnt.dll2000.80.1029.057,91621-Jun-200511:07x86
Semobj.dll2000.80.1029.0492,09621-Jun-200511:07x86
Semobj.rll2000.80.1029.0172,03217-Jun-200508:09Not Applicable
Snapshot.exe2000.80.1029.053,83221-Jun-200511:07x86
Sp3_serv_uni.sqlNot Applicable125,54014-Apr-200510:13Not Applicable
Sqlagent.dll2000.80.1029.028,67221-Jun-200511:07x86
Sqlagent.exe2000.80.1029.0311,87221-Jun-200511:07x86
Sqlakw32.dll2000.80.1029.0168,00121-Jun-200511:07x86
Sqlctr80.dll2000.80.1029.033,34421-Jun-200511:07x86
Sqldmo.dll2000.80.1029.04,215,36021-Jun-200511:07x86
Sqldumper.exeNot Applicable25,17221-Jun-200511:07x86
Sqlevn70.rll2000.80.1029.028,67217-Jun-200507:30Not Applicable
Sqlmaint.exe2000.80.1029.0156,22421-Jun-200511:07x86
Sqlmap70.dll2000.80.1029.0180,79221-Jun-200511:07x86
Sqlmmc.dll2000.80.1029.0188,99221-Jun-200511:07x86
Sqlmmc.rll2000.80.1029.0479,23217-Jun-200508:01Not Applicable
Sqlqry.dll2000.80.1029.0401,98421-Jun-200511:07x86
Sqlrepss.dll2000.80.1029.057,92021-Jun-200511:07x86
Sqlservr.exe2000.80.1029.07,725,13721-Jun-200511:07x86
Sqlsort.dll2000.80.1029.0590,39621-Jun-200511:07x86
Sqlvdi.dll2000.80.1029.045,64421-Jun-200511:07x86
Sqsrvres.dll2000.80.1029.0106,58821-Jun-200511:07x86
Ssmsgnet.dll2000.80.1029.033,34021-Jun-200511:07x86
Ssmslpcn.dll2000.80.1029.033,34021-Jun-200511:07x86
Ssmsqlgc.dll2000.80.1029.033,34021-Jun-200511:07x86
Ssnetlib.dll2000.80.1029.082,49221-Jun-200511:07x86
Ssnmpn70.dll2000.80.1029.025,14821-Jun-200511:07x86
Stardds.dll2000.80.1029.0123,45621-Jun-200511:07x86
Svrnetcn.dll2000.80.1029.0158,26821-Jun-200511:07x86
Svrnetcn.exe2000.80.1029.076,41621-Jun-200511:07x86
Ums.dll2000.80.1029.049,22821-Jun-200511:07x86
Xplog70.dll2000.80.1029.074,30421-Jun-200511:07x86
Xpweb70.dll2000.80.1029.098,87221-Jun-200511:07x86
Note Because of file dependencies, the most recent hotfix or feature that contains these 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.

Back to the top

MORE INFORMATION

For more information about the naming schema for Microsoft SQL Server updates, click the following article number to view the article in the Microsoft Knowledge Base:
822499 (http://support.microsoft.com/kb/822499/) New naming schema for Microsoft SQL Server software update packages
For more information about the terminology that Microsoft uses when it corrects software after the software is released, click the following article number to view the article in the Microsoft Knowledge Base:
824684 (http://support.microsoft.com/kb/824684/) Description of the standard terminology that is used to describe Microsoft software updates

Back to the top

APPLIES TO
•Microsoft SQL Server 2000 Desktop Engine (Windows)
•Microsoft SQL Server 2000 Developer Edition
•Microsoft SQL Server 2000 Enterprise Edition
•Microsoft SQL Server 2000 Personal Edition
•Microsoft SQL Server 2000 Standard Edition
•Microsoft SQL Server 2000 Workgroup Edition

Back to the top

Keywords: 
kbexpertiseadvanced kbbug kbfix kbhotfixserver kbqfe KB902852

Back to the top

Article Translations

 

Related Support Centers

Other Support Options

  • Contact Microsoft
    Phone Numbers, Support Options and Pricing, Online Help, and more.
  • Customer Service
    For non-technical assistance with product purchases, subscriptions, online services, events, training courses, corporate sales, piracy issues, and more.
  • Newsgroups
    Pose a question to other users. Discussion groups and Forums about specific Microsoft products, technologies, and services.