Export (0) Print
Expand All

Managing Desktop Engine Installation Package Files

SQL Server 2000

  Topic last updated -- January 2004

All supported methods of installing Microsoft® SQL Server™ 2000 Desktop Engine (MSDE 2000) require an installation package file (.msi). 

The recommended way to install MSDE 2000 is to run the Desktop Engine Setup.exe on either the command prompt or in an installation wrapper application. Do not run Setup.exe with a customized installation package file; it must be used with the .msi files (Sqlrun01.msi through Sqlrun16.msi) that are included on the SQL Server 2000 compact disc. Do not attempt to customize Sqlrun01.msi through Sqlrun16.msi. For more information about running Setup.exe, see Customizing Desktop Engine Setup.exe.

The latest versions of MSDE 2000 still provide the ability to build customized Windows Installer-based merge modules. This capability is provided only to support existing applications that still use merge modules. Using customized merge modules to install an instance of MSDE 2000 has these disadvantages:

  • The instance of MSDE 2000 cannot be patched independently of the application. Only a patch module supplied by the application vendor can be applied to the instance. MSDE 2000 service packs built by Microsoft cannot be applied to the instance.

  • The application vendor must build an MSDE 2000 patch file for every MSDE 2000 service pack, and then distribute those patch files to all customers. Customers cannot simply download and apply the latest Microsoft service pack.

  • Future releases of SQL Server will not include merge modules.

These disadvantages are true even if all you change is the product code globally unique identifier (GUID).

For more information about maintaining merge modules, see Using the SQL Server Desktop Engine Merge Modules.

SQL Server 2000 provides the following Desktop Engine installation package files to use as templates when you are creating a custom installation package file:

  • Sample.msi

    Supports only new installations; it does not support upgrading an instance of the Microsoft Desktop Engine (MSDE) version 1.0 to the SQL Server 2000 Desktop Engine.

  • SampleUpg.msi

    Used both for installing new instances of the SQL Server 2000 Desktop Engine and for upgrading instances of MSDE 1.0 to SQL Server 2000 Desktop Engine.

The Sample.msi and SampleUpg.msi files are provided only to build patch files for instances originally installed using them. Do not use either of these .msi files to install new instances of MSDE 2000 or to build customized installation packages to be used with a new application. The application should instead either use a wrapper installation application or have the user install an instance using Setup.exe. For more information, see Installing Desktop Engine.

The files supplied in the MSDE 2000 service packs cannot patch instances of MSDE 2000 that were installed using these .msi files. To patch such instances, you must instead build a patch file that can upgrade the instance to the latest service pack. For more information about building a patch file for instances installed using Sample.msi or SampleUpg.msi, see the readme file in the latest SQL Server 2000 service pack.

These .msi files are not included with MSDE 2000. They are, however, included with the other editions of SQL Server 2000, such as SQL Server 2000 Developer Edition. If you installed the SQL Server sample applications when running SQL Server 2000 Setup, the default location for these files is the folder C:\Program Files\Microsoft SQL Server\80\Tools\Devtools\Samples\Desktop.

Show:
© 2014 Microsoft