Overriding the Default SQL Run-Time Behavior

You can define the following Windows Installer properties to override default run-time behavior:

Windows Installer Properties for SQL
Property	Description
IS_SQLSERVER_CONNECTIONS_TO_VALIDATE	Overrides the connection(s) that will be tested when clicking the Next button on the SQLLogin dialog. Specify multiple connections by separating each with a semicolon. By default, all the connections in the ISSQLConnection table will be validated.
IS_SQLSERVER_CXNS_ABSENT_FROM_INSTALL	Specifies one or more SQL connections that should be skipped during installation or uninstallation. To specify more than one SQL connection, separate each with a semicolon (;). To skip all of the SQL connections, set the value of this property to ALL. Using this property is helpful if you cannot uninstall a product because of a SQL scripting error.
IS_SQLSERVER_DO_NOT_USE_REG	Specify not to use the stored SQL Server login information written in the registry. Since the SQLLogin dialog is not displayed in maintenance and uninstall modes, InstallShield stores the login information specified during installation. If you do not want this behavior, set the IS_SQLSERVER_DO_NOT_USE_REG property.
IS_SQLSERVER_LOCAL_ONLY	Specify to show only the local SQL Server in the SQL Server browse combo box and list box controls. By default, the SQL Server(s) on the network will be listed.

For Windows Installer–based projects, all connections are linked to the standard SQL Login dialog. To display multiple SQL Login dialogs, you can copy the SQL dialogs from the Dialogs view and modify their behavior and events similar to the SQL default dialogs. Remember to create new properties, and set them in the connection’s Advanced tab of the SQL Scripts view. You will use those new properties when you modify the copies of the SQL dialogs that you made.