The SQL Scripts page

This page allows you to configure SQL scripts that will be executed at run time. You might use this page if the application you are installing depends on certain database content and configuration. This page eliminates the need to require end users to configure databases manually.

Add a New Predefined SQL Connection

Use the [ New SQL Connection ] toolbar button, the "New Predefined SQL Connection" context menu item or press the Ins key.

Add a New Custom SQL Connection

Use the [ New SQL Connection ] toolbar button, the "New Custom SQL Connection" context menu item.

Add a New SQL Script

Use the [ New SQL Script ] toolbar button, the "New SQL Script" context menu item or press the + key.

SQL Transactions

By default an ODBC driver is in autocommit mode; that means each statement is committed immediately after it is executed. Advanced Installer allows you to configure transaction isolation units. You can group one or several SQL script files in a single transaction unit, hence ensuring that the query changes will be committed atomically. At the beginning of each transaction unit, the ODBC driver is put in manual commit mode, and at the end of the unit the changes are committed (if everything went ok), otherwise all changes from the isolation unit are rolled back. After exiting a transaction unit, the ODBC driver is put back in autocommit mode, so that your following, non-isolated, batch files will execute/commit automatically.

For details about SQL transactions and Advanced Installer implementation behaviour, please see this article.

Renaming an SQL Connection or SQL Script

Use the "Rename" context menu item or press the F2 key while a SQL connection or SQL script is selected.

Deleting an SQL Connections or Scripts

Use the [ Delete ] toolbar button, the "Delete" context menu item or press the Del key while a SQL connection or SQL script is selected.

Impersonate installing user

Use the "Impersonate installing user" context menu item while "Database Server" is selected in the tree pane. You can check this option if you want to run all SQL scripts as the user installing the application, not under the Local System account (this applies only to Trusted SQL Connections that use Windows integrated authentication).

You can set the order of execution for SQL connections and scripts by drag & drop in the tree.