Specifying the Order for Running Multiple SQL Scripts That Are Associated with a Connection

InstallShield 2016

Project • This information applies to the following project types:

If you add more than one SQL script to a SQL connection in your project, you can specify the order in which the installation runs those SQL scripts on the target machine. The procedure for specifying the order differs for Windows Installer–based and InstallScript-based projects.

Specifying the SQL Script Order in Basic MSI, DIM, and InstallScript MSI Projects

The order in which a connection’s SQL scripts are listed in the SQL Scripts view of a Basic MSI, DIM, and InstallScript MSI project is the order in which the installations run the SQL scripts. For example, if you create a connection in the SQL Scripts view and add two SQL scripts to that connection, the script that is listed first under the SQL connection is the one that the installation runs first.

To change the order in which a connection’s SQL scripts are run:

The next time that you build and run the installation, the order is updated.

Specifying the SQL Script Order in InstallScript Projects

By default for InstallScript installations, batch mode for SQL scripts is disabled; therefore, the order in which a connection’s SQL scripts are run corresponds with the order in which the installation processes the associated components.

If you want to be able to override this default behavior and specify a particular order for running the SQL scripts, you can do so by enabling the batch mode in the SQL Scripts view.

To enable or disable batch mode:

Batch mode is enabled if the Batch Mode command has a check mark; it is disabled if the command does not have a check mark.

The SQLRTGetBatchList function returns the list of components that are associated with SQL scripts that need to be run when batch mode is enabled. For more information, see SQLRTGetBatchList.

Open topic with navigation