About Engineering with database packaging (2)-Automatic Installation of custom MSDE instances

During this period, the project on hand is close to the end, but the packaging problems that were not paid much attention to in the past are gradually highlighted. This not only refers to the creation of a installable project installation package, there are also information about the installation of database instances in the absence of runtime environments and the installation and recovery of database data. Here, we will share with you the experiences of packing MSDE into the installation program.

When your project is basically tested and ready for release, creating a simple automatic installation package for users will become another problem to be solved after coding, and whether the project development is complete or not, you should have an initial experience during installation.

The following describes how to add the automatic installation and merging module of Microsoft SQL Server 2000 Desktop Engine (MSDE) to the project:

1. First, you need to download the SP3 installation package of msde2000. Can be downloaded from the following link, URL: http://www.microsoft.com/ SQL /downloads/2000/sp3.asp

2. after the download is complete, you can install or decompress the package to the local hard disk by using a zip file. You can see the three directories MSI, MSM, and setup and other files, the figure in the MSM folder is the msde2000 merging module described in this article.

3. add an installation project (for example, mysetup1, path: C: \ mysetup1) to your project, and add project output according to the normal steps ), select the output file (primary output) and content file (content files.

4. add the Merge Module (merge Moudle), select Browse, specify to your MSDE's MSM folder, and select all the files (REPL. MSM, repl_res.msm, dmo_res.msm, and DMO. (Optional.

5. Set the searchpath in the properties of the installation project to specify the path where your MSM is located (in this case, you need to add two: path \ MSM and path \ MSM \ 1033 ).

6. if you set other attributes of the installer, we will not mention it for the moment. This will allow you to compile your installation project. After the compilation is successful, you can go to C: \ mysetup1 \ debug \ see your packaging project mysetup. MSI.

7. This is a project package. Next we need to modify the installation package so that it can automatically install an instance of MSDE after installing the program (assuming the Instance name is myserver ). Now we need a Ms tool orca: http://support.microsoft.com/default.aspx? SCID = KB; en-US; 255905 after orca is installed, you can use this tool to modify our mysetup1.msi.

8. Use Orca to open the installation package file mysetup. MSI, find the table property, add row, and enter sqlinstancename in propetry, and enter the Instance name myserver in value. For other parameters, see: http://support.microsoft.com /? Id = 810826 and http://support.microsoft.com/default.aspx? SCID = KB; en-US; 281983

9. I have not succeeded in all the parameters related to the password, that is, sqlsapwd. this parameter is used with sqlsecuritymode, but I have never set it successfully and the password is always blank, somehow!

10. Select the table installexecutesequence, find the setpropsqlmsdeinstalled action, change 206 to 102, find removeexistingproducts, and change 1525 to 6601. Save and exit!

 

In this case, run your installation package on a machine without an SQL environment. After the program is installed, the myserver instance of MSDE is automatically installed, and after the machine is restarted, automatically Start an SQL server instance.

 

About Engineering with database packaging (2)-Automatic Installation of custom MSDE instances