This tab has the following components:
The following options control Interactive SQL behavior when running SQL script files.
When an error occurs Select one of the following options to control how Interactive SQL responds when it encounters an error while executing statements:
Continue The error is ignored and Interactive SQL continues executing statements.
Exit Interactive SQL shuts down.
Notify and Continue The error is reported, and the user is prompted to press Enter or click OK to continue.
Notify and Exit The error is reported and the user is prompted to press Enter or click OK to shut down Interactive SQL.
Notify and Stop The error is reported and the user is prompted to press Enter or click OK to stop executing statements.
Prompt Interactive SQL prompts the user to see if they want to continue. This is the default.
Stop Interactive SQL stops executing statements.
When you are executing a .sql file, the values Stop and Exit are equivalent. If you specify either of these values, Interactive SQL shuts down.
See also on_error option [Interactive SQL].
Echo SQL script files to log Select this option to have Interactive SQL log executed SQL statements to the log file. This option is most useful when you use the READ statement to execute an Interactive SQL script file or when you run a script file in Interactive SQL by choosing File » Run Script. Logging must be turned on for this option to take effect.
By default, SQL script files are copied to the log. See echo option [Interactive SQL].
Select one of the following options to specify which directory Interactive SQL uses first when browsing for files.
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.
Current folder If you select this option, the initial directory used by the browser is the current folder, as defined by the operating system.
When the fast launcher is turned on, Interactive SQL will remain in memory for a configurable length of time after you close it (default is 30 minutes). If you restart Interactive SQL within this time, it will start quickly. If you do not restart Interactive SQL within this time, the process will terminate and will release its resources to the operating system.
The fast launcher process requires additional 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. 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 Interactive SQL Fast Launcher Configuration window where you can configure the TCP/IP port used by the fast launcher and set the inactivity timer.
On Windows, you can make Interactive SQL the default editor for .sql files.
Make Interactive SQL the default editor for .SQL and plan files Select this option to make Interactive SQL the default editor for .sql and graphical plan files on Windows. SQL Anywhere graphical plan files have the extension .saplan.
If you select this option, Windows uses Interactive SQL to automatically open the file when you double-click it. Interactive SQL does not run the file automatically.
Discuss this page in DocCommentXchange.
|Copyright © 2014, SAP AG or an SAP affiliate company. - SAP Sybase SQL Anywhere 16.0|