The Script Editor works pretty much the same as the SQL Editor. It has the same construct for SQL Pages and its output goes to the Server Output window - Tools | Server Output.
Note: There is no Script Editor available on ADO or ODBC connections.
Execute (Very) Large Scripts
If you want to execute very large scripts, better not use the Script Editor. As the Script Editor is an interactive editing tool, it requires syntax highlighting, parsing for scroll bar size etc. This can be a slow process on large scripts.
To execute (very) large scripts, use the Script Runner instead, accessible via the tool bar button or Tools | Script Runner.
Executing Scrips
You can load or create script in the Script Editor and execute them.
If an error occurs, it will show a dialog that allows you to ignore the error and continue or to abort the current script. If you don't want this dialog to show, edit the Script Preferences.
Script Editor Error Dialog
The Ignore all errors for this run checkbox allows you to ignore any errors for the current run. Once you use the Run (F9) button, this checkbox is reset.
Linking Scripts
The Script Editor in Database Workbench supports the INPUT directive. Syntax is:
INPUT 'path\filename.extension';
Database Workbench will load the filename identified by "filename.extension" and execute it 'inline'. After the loaded script has finished executing, it will continue executing the calling script. Loaded scripts will be shown on a seperate SQL Page.
If no path information is used, the current path will be used in the attempt to load the secondary script file.
Note:
The Script Editor uses the same transaction/autocommit setting as the SQL Editor - the other tab in this editor window. For more information about transactions, see SQL Editor