The General tab of the Options dialog in Interactive SQL has the following components:
Commit The following options let you select when to commit changes to the database. You can also commit manually by entering an explicit COMMIT command whenever appropriate.
After each command Select this option to commit changes to the database after each SQL statement is executed.
On exit Select this option to commit changes to the database when you exit your Interactive SQL session. This is the default setting.
For more information, see .
Command files The following options control Interactive SQL's behavior when running command files.
When an error occurs Select an option to control how Interactive SQL responds when it encounters an error while executing statements from a command file. Depending on the option you choose, Interactive SQL can continue executing the file, stop executing the file, or shut down. The default setting is Prompt.
For more information about configuring how Interactive SQL responds to errors while executing statements from a command file, see .
Echo command files to log If you select this option, Interactive SQL logs SQL statements that are executed from command files to the log file.
By default, command files are copied to the log.
For more information, see .
When browsing for files, where should the browser start? Select one of the following options to specify which directory Interactive SQL uses first when browsing for files. If you wish to use this setting in subsequent Interactive SQL sessions, click Make Permanent after selecting one of the following options.
Last folder used If you select this option, the initial browser directory is the one where you last used the file browser. This is the default setting.
Current folder If you select this option, the initial directory used by the browser is the current folder, as defined by the operating system.
Fast Launcher
The fast launcher is designed to reduce Interactive SQL's startup time. When the fast launcher is turned on, the fast launcher process (dbisqlg.exe for Interactive SQL) starts when you log in. The fast launcher is only available on Windows platforms. You can change the settings for the fast launcher on the Interactive SQL Options dialog (opened by choosing Tools > Options in Interactive SQL).
Sybase Central has its own fast launcher process (scjview.exe) that is turned on and off separately from the Interactive SQL fast launcher. You can configure the Sybase Central fast launcher from the Sybase Central Options dialog (opened by choosing Tools > Options in Sybase Central).
Note that the fast launcher process requires a significant amount of memory, and the impact on application startup time depends on your system configuration.
Enable fast launcher Select this option to turn on the fast launcher. The fast launcher is turned on by default. If you want to turn the fast launcher off, clear this checkbox. You must log out and log in again for these settings to take effect.
Configure Opens the DBISQL Fast Launcher Configuration dialog where you can configure the TCP/IP port used by the fast launcher and set the inactivity timer.
The fast launcher uses a TCP/IP port on your machine. If another program is already using this port, you can change the port number used by the fast launcher in this dialog.
When the fast launcher is not used for the amount of time specified in the inactivity timer, it shuts down, which frees up memory for other applications. By default, the inactivity timer is set to never shut down.
File Association On Windows platforms, you can make Interactive SQL the default editor for .SQL files.
Make DBISQL the default editor for .SQL files Select this option to make Interactive SQL the default editor for .SQL files on Windows.
Windows uses Interactive SQL to automatically open the file when you double-click on it. Note that Interactive SQL does not run the file automatically.