The Batch Run is designed to give the most accurate result by providing options for obtaining the most accurate run time taking into account the effects of caching the data, indexes and the SQL statements. This section allows you to select one of the four options best suited to your SQL statement.
|Run to retrieve||Description|
Specify to retrieve the run time for processing All Records.
First n Records(s)
|Specify to retrieve the run time for processing n records where you specify the number of records retrieved.|
|Retrieve the run time by executing||Description|
Run SQL options
Select one of the following options:
Include trace statistics
|Select this checkbox to include trace statistics in the retrieved SQL.|
The Batch Run Schedule criteria enable you to schedule when to start and stop the Batch Run.
Specify to start the Batch Run immediately.
Date and Time
Specify to start the Batch Run at a specific date and time.
Specify to start the Batch Run after it has been running for a specified number of hours and minutes.
Specify to run the entire Batch Run until all SQL statements are executed.
Date and Time
Specify to terminate the Batch Run on the specified date and time.
Specify to terminate the Batch Run after it has executed a specified number of hours and minutes.
Terminate immediately (Date/Time and Duration only)
Specify to terminate the currently executing SQL statement and all remaining unexecuted SQL statements.
Terminate after currently executing SQL is finished (Date/Time and Duration only)
Specify to finish running the currently executing SQL statement and do not run the remaining unexecuted SQL statements.
In order to obtain the correct result during the Batch Run or Run Time of alternative SQL statement, the SQL statement executes against the database. However, when executing UPDATE, INSERT, DELETE statements, any changes to the database are rolled back.
Note: For UPDATE, INSERT and DELETE SQL statements, while retrieving the run time and run result you may encounter the following Adaptive Server error message:
Can't allocate space for object 'syslogs' in database 'database_name' because the 'logsegment' segment is full. If you ran out of space in syslogs, dump the transaction log. Otherwise, use ALTER DATABASE or sp_extendsegment to increase the size of the segment
This is due to the lack of space in system table (syslogs), in which all changes to the database are recorded. Empty the transaction log in the database and re-execute. Use the following command in the SQL Workshop module:
DUMP TRANSACTION database_name WITH TRUNCATE_ONLY
The Batch Run Details window displays a summary of the run time information for all SQL statements executed. The Batch Run Details window displays after the batch run process is completed unless the Show details on next batch run checkbox in the Batch Run Details window is unchecked.
To review the Batch Run Details window after a Batch Run
Select View | Show Batch Run Details when the SQLOptimizer window is active.
If a SQL statement has a database error during the Batch Run, an explanation of the error is included in the Batch Run details.