Article ID: 814618
Article Last Modified on 11/14/2007
APPLIES TO
- Microsoft SQL Server 2000 Service Pack 3
SUMMARY
SQL Server 2000 Service Pack 3 (SP3) is available as three separate file packages. To download the file packages, visit the following Microsoft Web site:
SQL Server 2000 Service Pack 3
MORE INFORMATION
The files you must download and install depend on the SQL Server 2000 components that you are running. Note that you can have any combination of these SQL Server components running on a single computer.
SQL Server Desktop Engine
If you are running SQL Server Desktop Engine (also known as MSDE 2000), you must either download and apply SQL2KDeskSP3.exe, or get a patch file from the vendor of the application that installed their instance of MSDE.
SQL Server 2000 Developer, Personal, Standard, or Enterprise Edition
If you are running the Developer, Personal, Standard, or Enterprise Edition, you must download and apply SQL2KSP3.exe.
SQL Server 2000 Analysis Services
If you are running Analysis Services, you must download and apply SQL2KASP3.exe.
Important This service pack can only be installed on computers that are running SQL Server 2000, MSDE 2000 (version 2.0), or Analysis Services 2000. After you determine what edition you have installed, you must confirm that you are running the 2000 version before you install this service pack. To determine what version of SQL Server you are running, see the following article in the Microsoft Knowledge Base:
321185 HOW TO: Identify Your SQL Server Service Pack Version and Edition
How to Determine If You Are Running MSDE or SQL Server
To determine whether you have MSDE or one of the SQL Server editions, open the Windows Regedit utility, and look for a registry value that is named ProductCode. For example:
Named Instance
For a named instance:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\<Instance Name>\Setup
Default Instance
For a default instance:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSSQLServer\Setup
If one of these keys exist but there is no ProductCode, the instance is one of the SQL Server 2000 Editions (such as Enterprise, Enterprise Evaluation, Standard, Developer, or Personal) and you must apply SQL2KSP3.exe.
If a ProductCode entry is present, the instance is MSDE and you must apply a patch file that is based on the ProductCode key. The ProductCode is unique for every instance of an MSDE installation. The 16 unmodified MSDE packages that were included with SQL Server each have their own unique name. A table that lists these names is available in the following Microsoft Knowledge Base article:
311762 INF: How to Identify Which MSI File Was Used for an Existing MSDE Installation
How to Determine How to Upgrade an Instance of MSDE
How you upgrade MSDE will depend on your ProductCode:
- If the ProductCode of an MSDE instance matches any of the first 16 product codes in the table referenced in 311762, it is one of the 16 MSDE packages that was provided with SQL Server. You can upgrade it by using the SQL2KDeskSP3.exe file.
- If the ProductCode differs from the first 16 product codes, or its listing corresponds with instance names such as NETSDK, MSAC, or ProjectServer, it is a customized installation.
- Customized installations include MSDE customized for Microsoft products such as Microsoft Application Center 2000 or Microsoft .NET Framework SDK, and third-party products. You cannot upgrade these instances of MSDE 2000 by using the files on the download page. To upgrade these instances of MSDE to Service Pack 3, you must obtain a patch file from the vendor of the application that installed that instance of MSDE.
How to Determine If You Are Running Analysis Services
To determine if you are running Analysis Services, follow these steps:
- On the Start menu, click Control Panel.
- If you are running Microsoft Windows XP, click Administrative Tools.
- Select Services.
If the MSSQLSERVEROLAPSEVICE service is listed, you have Analysis Services installed. To upgrade, you must download and apply SQL2kASP3.exe.
Additional Ways to Determine Your Edition of SQL Server 2000
You can also find edition information through the following methods; however, none of the methods listed will indicate if you have a customized installation of MSDE:
If the instance is running, you can connect with either Query Analyzer or osql and run
SELECT @@VERSION
The last line that is returned indicates what edition you are running.
If the instance is running, you can connect with either Query Analyzer or osql and run
SELECT SERVERPROPERTY(‘EDITION’)
This query will return one of the following:
- Desktop Engine
- Developer Edition
- Enterprise Edition
- Enterprise Evaluation Edition
- Personal Edition
- Standard Edition
- If the instance is not running and you do not want to start it before you try to apply a fix, you can look at a SQL Server error log. If the user selects the defaults during setup, the error logs are located in one, or both, of these folders:
Default Instances
C:\Program Files\Microsoft SQL Server\MSSQL\Log
Named instances
C:\Program Files\Microsoft SQL Server\MSSQL<InstanceName>\Log - Open any of the numbered error files (errorlog, errorlog.1, errorlog.2, and the rest) in Notepad. The edition of SQL Server is reported at the top of the file.
REFERENCES
311762 INF: How to Identify Which MSI File Was Used for an Existing MSDE Installation
813115 FIX: W32.Slammer Worm Exploits MSDE 2000 Vulnerability in Application Center 2000
814046 PSVR2002: Project Server Users with MSDE 2000 Installed May Be Vulnerable to Slammer Worm
Additional query words: MSDE upgrade patch
Keywords: kbhowto KB814618
