General Tab

InstallShield 2016 » SQL Scripts View » SQL Connection

Project • The SQL Scripts view is available in the following project types:

•

Basic MSI

•

DIM

•

InstallScript

•

InstallScript MSI

You can configure the following settings on the General tab for a SQL connection in the SQL Scripts view.

General Tab Settings for a SQL Connection

Setting

Description

Catalog Name

Note • Creating a new application catalog based on Oracle database settings is equivalent to creating a new database based on SQL Server settings in InstallShield. However, terminology is slightly different in reference to Oracle. In Oracle, the catalog is equivalent to the schema being used for every new application catalog. Therefore, note the semantic differences between “catalog” and “database” when understanding the differences between SQL Server and Oracle support in the documentation.

Enter the name of the SQL catalog to which you want to create a connection during the installation.

If you leave this setting blank, the installation attempts to connect to the default catalog during the connection test phase at run time. If the catalog you specify is not found at that time, the installation still creates the specified catalog upon connection verification. This is because the Create Catalog If Absent option is selected in InstallShield by default.

Create Catalog If Absent

This option is selected by default. If this option is selected, the installation creates the specified catalog upon connection verification at the SQLLogin dialog at run time.

You should note that when the Create Catalog If Absent option is selected, different SQL commands are issued for the various supported server types.

For Microsoft SQL Server, Microsoft Windows Azure SQL, and MySQL, selecting this option results in the following:

CREATE DATABASE CatalogName

CatalogName is the value that you specify in the Catalog Name box on the General tab for a connection in the SQL Scripts view.

For Oracle, selecting the Create Catalog If Absent option results in the following:

CREATE USER CatalogName IDENTIFIED BY CatalogName DEFAULT TABLESPACE USERS QUOTA UNLIMITED on USERSGRANT CONNECT TO CatalogNameGRANT DBA TO CatalogNameALTER USER CatalogName DEFAULT ROLE ALL

Therefore, you should note that for Oracle, the schema name serves as the user name and password for the selected catalog by default.

Create Catalog If Absent (cont.)

If you do not wish to use the Create Catalog If Absent option to create a catalog, you can run a customized script to create a catalog. When you run a custom script, you can use the Runtime tab for the script in the SQL Scripts view to schedule the execution of the script during login.

For more information about running a customized script, see the following instructions:

•

Creating a Sample Installation that Creates a SQL Server Database by Running Customized SQL Script

•

Creating a Sample Installation that Creates an Oracle Schema by Running Customized SQL Script

Project • In the case where the Create Catalog If Absent option is cleared during installation design and the catalog is not found at run time, the installation behavior slightly differs for the following project types at run time.

•

For Basic MSI, DIM, and InstallScript MSI projects—The installation connects to the default catalog at the SQLLogin dialog during run time to test the connection. This enables the installation to run custom code during the InstallExecuteSequence. However, the presence of the catalog needs to be guaranteed when the SQL scripts that are specified in your project are executed. The run time re-establishes the connection with the specified catalog to run the scripts. If the catalog is absent at this point, the connection fails.

•

For InstallScript projects—The catalog needs to be present at the SQLLogin dialog since the run time holds the connection until the installation ends, once the connection is established. In this scenario, you can run custom InstallScript code to create the catalog before the SQLLogin dialog shows up to override the default behavior.

Default Target Server Name

For Microsoft SQL Server and MySQL, you can enter the machine name of the target SQL Server here. This setting is optional.

For Microsoft Windows Azure SQL, enter a fully qualified server name in the following format:

tcp:ServerName.database.windows.net

Following is an example:

tcp:wbzdh64drd.database.windows.net

For Oracle client machines with Oracle 11g client software installed, enter a SQL connection URL string in the following format:

//host: [port] [/service name]

The following is an example of what you would type to connect to a specified remote Oracle machine:

//sch01jsmithrxp.installshield.com:1521/ORCL

You can also specify a local net service name if you have tnsnames.ora configured on the client machine. For more details, consult the Oracle Support Web site.

Connect using

Select the type of authentication you want to use to connect to the specified catalog. For SQL Server Authentication, enter login and password information for the targeted server.

Comments

Enter comments about this connection. These comments are not displayed to the end user.

General Tab

InstallShield 2016 Help Library

August 2016