Article ID: 311762
This article was previously published under Q311762
After you install Microsoft SQL Server 2000 Desktop Engine (also known as MSDE 2000), there are three ways to identify which .msi file the MSDE 2000 setup used. MSDE 2000 includes 16 standard .msi files, and other products may include their own customized MSDE .msi file. Each .msi file is a separate package that allows you to install an instance of the Desktop Engine.
The identification of the correct .msi file is important because you have to use a specific install package to apply service packs to the existing Desktop Engine installation. For example, if you used Sqlrun01.msi to install the original MSDE 2000, then you must use Sqlrun01.msp to upgrade it to Service Pack 2 (SP2). For sqlrun02.msi, you must use Sqlrun02.msp and so forth.
For an existing MSDE 2000 instance, here are three different ways to identify the .msi file the setup used:
or this registry value for a named instance:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\<instance_name>\MSSQLServer\CurrentVersion\Language
This registry value stores a locale ID. Below is a list of the possible locale IDs for MSDE 2000:
Collapse this tableExpand this table
For more information on Microsoft Application Center and Microsoft .Net Framework, please visit the following Microsoft Web sites:
Application Center 2000
.NET Framework Developer Center
Article ID: 311762 - Last Review: July 30, 2012 - Revision: 6.0
Retired KB Content Disclaimer
This article was written about products for which Microsoft no longer offers support. Therefore, this article is offered "as is" and will no longer be updated.