Chat now with support
Chat with Support

SQL Optimizer for DB2 LUW 4.4.1 - Installation Guide

Retrieve Run Result

Note: This feature is available for only SQL alternatives, not index-set alternatives.

To retrieve the SQL statement results from the database

In the SQL Optimizer window, select the SQL alternative, and click image\B_RunResult.gif.

If the SQL statement contains a result set, the SQL Result window displays, showing all data retrieved. Otherwise, an information dialog box showing the number of rows affected displays.

In the SQL Result window, the first rows of the result set are displayed as soon as they are returned from the database. Therefore, the time it takes for you to see the result does not equal the time measured by the run- time functions to retrieve either the first record or all records run time. Run Result only retrieves enough records to display in the window; the complete result set is not retrieved until you view the last records.

To terminate the Run Result process

Click image\B_AbortRunResut.gif.

Commit or Rollback

Two types of action, commit or rollback, can be made after the Run Result has been executed for a UPDATE, INSERT, or DELETE SQL statement depending on which window you are in when you execute the Run Result function.

For the original SQL statement

When you retrieve run results for the original SQL statement (displayed as <Edit SQL>), you are prompted to commit or rollback for UPDATE, INSERT, and DELETE SQL statements.

For the SQL alternatives

For the SQL alternatives, all rows affected by UPDATE, INSERT, and DELETE SQL statements are rolled back automatically.

New Database Session

When you log on to DB2 LUW from SQL Optimizer, it connects to the database and maintains this database connection throughout the application execution. Another database session is required for the Run Result processing. This connection is established when the Run Result function is executed and dropped after all the records have been retrieved.


Related Documents