SQL Server 2000 Desktop Engine (MSDE 2000) provides new prospects for application desktops and shared programs for application developers, which can spread freely, and if customers or general users want to expand their programs to thousands of users or These programs can also be easily migrated to SQL Server 2000 technology when TB data.
E.g:
Developers can provide an introduction or trial version of the original product that is attached to SQL Server 2000. Developers can point to complete expansion in the product, that is, if the customer wants to expand the application to serve the entire enterprise, no need to upgrade or conversion. The company developers can completely borrow their original background they have developed in software, ensuring that the original use of the desktop or small department can be used for the entire bus with the entire business, without having to change any line code.
Authorized developers can freely spread MSDE 2000 scenarios, which can be built in Microsoft Visual Studio 6.0 Professional and Visual Studio 6.0 Enterprise version, or by Microsoft Office 2000 Developer. See the "General User Authorization Contract" file with full dispersion cloth and terms of terms.
The scattered method has the MSDE 2000 application developer, that is, the ability to install the relevanceful associated database engine, which is a part of the custom application installer, completely matched with SQL Server 2000. Using MSDE 2000 Applications can store data on desktop engines, and their configuration and resources are dynamic management, and thus unlock the need for additional graphical tools and management utilities. This allows MSDE 2000 to become an ideal database embedded in the desktop and notes.
There are two ways to allow the application developers to build MSDE 2000 installation into their application installation. After the database engine is installed, developers can use standard SQL Server API to build and manage the database objects.
The MSDE 2000 using MSDE 2000 and Windows Installer uses Windows Installer technology is included in a set of Windows Installer consolidation modules. Application developers use these merged modules, install an MSDE 2000 execution individual during the custom application installation. The completed method is to integrate the merged module into a standard Windows Installer installer, or let the self-reservation application installation directs the Windows Installer to the MSDE 2000 execute individuals.
The method of reducing the hindrance of the embedded database engine is to exclude a specific function merge module (such as a replication, decentralized management object, etc.), and these modules are unlikely to use.
To learn how to use Windows Installer technology to integrate MSDE 2000 to your app, see the Merging The Desktop Engine Into Windows Installer of the MSDN® website.
Installing MSDE 2000 using non-Windows Installer to install the MSDE 2000 to execute individuals, MSDE 2000 provides a setup.exe utility file for your application. This file opens a shell to call Windows Installer to install the MSDE 2000 to execute an individual. You can define the setting of the custom SETUP.EXE to install the MSDE 2000. These settings can be specified by a command prompt parameter or a .ini file. With the setup.exe utility, you must spread 16 MSDE 2000 installation packages (SQLRun ##. Msi). Each installed program package is unique MSDE 2000 execution individual.
Before trying to install the MSDE 2000, the application installer should first determine that the individual name is not yet implemented by the individual, and the computer does not have more than 16 execution individuals (or 15 named execution individuals). Otherwise, the entire domain unique identification (GUID) may occur. SQL Server 2000 provides two API features to perform these checks. For more information on how to manage MSDE 2000 installation program, see MSDN's Managing Desktop Engine Installation Package Files.
If Windows Installer is installed on the target computer, the installation utility will also check. If you can't find Windows Installer, install the utility will try to install, then continue to select unused MSDE 2000 installation packages for this specific installation.
This is quite important if your application supports multiple MSDE 2000 executing individuals. Installing MSDE 2000 without building your own Windows Installer packaging software, increase the risk of GUID conflicts.
If your app does not support multiple MSDE 2000 executing individuals, and you determine that the target computer does not install the exact MSDE 2000 execution individual, you can disperse or create a Windows Installer package software (with guid), and When calling the msiexec.exe utility, pass this Windows Installer package software file name. In this case, you will not need to spread all 16 MSDE 2000 installation packages.
To learn more about how to use the SETUP.EXE utility of MSDE 2000, see the SQL Server 2000 Desktop Engine Setup on MSDN.
Manually install an MSDE 2000 database Execute an individual without using a Windows Installer architecture installation program, or you can directly call Windows Installer to install the MSDE 2000 to perform individuals. It is also done by direct call Msiexec.exe. The general completion is to have available DLLs in the application installation, and the DLL contains a callback function, which can be managed by the MSDE 2000 Windows Installer consolidation module.
To see an example installer program, see the SMDN Desktop Engine Installation Sample.
Integrate MSDE 2000 with Office Application
Installing MSDE 2000MSDE 2000 does not automatically install during Microsoft Office XP installation. The installation file is located in the / MSDE2000 folder of Office XP CD. Please perform setup.exe to start installing.
After installing MSDE 2000 to your computer, if you are performing a Microsoft Windows® 98 or update version, you may need to start the SQL Server service administrator (press [MSSQLSERVER] on the two lower work columns, then press [Start / Continue ]). MSDE 2000 will automatically start on the computer that performs Microsoft Windows NT® 4.0 or updated. You may want MSDE 2000 to automatically start on a Windows 95 or updated version of the computer, and the method is to check [Automatic start service when booting when booting when booting automatically] in the [SQL Server Service Administrator] window.
