FAST_SELECT block

The FAST_SELECT block and its underlying SQL structure represents the SQL that Optim™ High Performance Unload natively supports. The underlying SQL structures are defined in the sections following this block.

Attention: The FAST_SELECT block requires a semicolon at the end.
Figure 1. Fast select block

1  SELECT
1+ ,
1 *
1 column name
1 literal
1 expression
1 Db2 variable
2  FROM
1 tablename
1 creator.tablename
1 SYSTEM.creator.tablename(1)(2)
1 period_condition
4?  WHERE search_condition
4  ;
Notes:
  • 1 If the SELECT statement refers to a table name qualified with the SYSTEM tenant name, the tenant to be considered by the execution must be the SYSTEM tenant as well.
  • 2 If the SELECT statement refers to a table name qualified with a tenant name, this tenant name must be SYSTEM.

Processing Db2® views with Optim High Performance Unload

Optim High Performance Unload can natively process Db2 views, including views for temporal tables. The following conditions must be met, so that Optim High Performance Unload can process a view natively:
  • The catalog information must be retrieved from a live database and not from a backup image.
  • Optim High Performance Unload must understand the syntax of the creation statement of the view. If the creation statement is too complex, the processing is passed to Db2, and if the DB2 option is set to NO, Optim High Performance Unload returns an error.