Reads in options from the specified environment variable or configuration file.

If both the environment variable and configuration file exist with the same name, the environment variable is used. See Configuration files.

If you want to protect passwords or other information in the configuration file, you can use the File Hiding utility to obfuscate the contents of the configuration file. See File Hiding utility (dbfhide).

Specifies connection parameters. If Interactive SQL cannot connect, you are presented with a window where you can enter the connection parameters. If you do not specify both a user ID and a password, the default UID of DBA and PWD of sql are assumed. See Connection parameters.

Specifies a command delimiter. Quotation marks around the delimiter are optional, but are required when the command shell itself interprets the delimiter in some special way.

This option overrides the setting of the command_delimiter option. See command_delimiter option [Interactive SQL].

Opens (but does not run) the file called filename in the SQL Statements pane.

If the -f option is given, the -c option is ignored; that is, no connection is made to the database.

The file name can be enclosed in quotation marks, and must be enclosed in quotation marks if the file name contains a space.

If the file does not exist, or if it is really a directory instead of a file, Interactive SQL prints an error message and then quits.

If the file name does not include a full drive and path specification, it is assumed to be relative to the current directory.

This option is only supported when Interactive SQL is run as a windowed application.

Runs Interactive SQL as a console application, with no windowed user interface. This is useful for batch operations.

If you specify either dbisql-statement or dbisql-script-file, then -nogui is assumed.

In this mode, Interactive SQL sets the program exit code to indicate success or failure. On Windows operating systems, the environment variable ERRORLEVEL is set to the program exit code. See Software component exit codes.

Controls what happens if an error is encountered while reading statements from a script file. It is useful when using Interactive SQL in batch operations. This option overrides the on_error setting. See on_error option [Interactive SQL].

Define one of the following supported behavior values:

Suppresses output messages. Sets the utility to run in quiet mode. This is useful only if you start Interactive SQL with a statement or script file. Specifying this option does not suppress error messages, but it does suppress the following:

Specifies that UltraLite databases are the default. Interactive SQL customizes the options available to you depending on the type of database you are connected to.

By default, Interactive SQL assumes that you are connecting to SQL Anywhere databases. When you specify the -ul option, the default changes to UltraLite databases. Regardless of the type of database set as the default, you can connect to either SQL Anywhere or UltraLite databases by choosing the database type from the Change Database Type dropdown list on the Connect window.

For more information about connecting to UltraLite databases from Interactive SQL, see Interactive SQL for UltraLite utility (dbisql).

Displays the version number of Interactive SQL. You can also view the version number from within Interactive SQL; from the Help menu, click About Interactive SQL.

Scans statements but does not execute them. This is useful for checking long script files for syntax errors.

For detailed descriptions of SQL statements and Interactive SQL statements, see SQL language elements.

Execute the SQL statement or execute the specified dbisql-script-file.

If you do not specify a dbisql-statement or dbisql-script-file, Interactive SQL enters interactive mode, where you can type a statement into a command window.