SQL/MX 2.x Reference Manual (H06.04+)

SQL/MX Statements
HP NonStop SQL/MX Reference Manual540440-003
2-46
CONTROL TABLE Statement
CONTROL TABLE Statement
Considerations for CONTROL TABLE
Examples of CONTROL TABLE
The CONTROL TABLE statement specifies a performance-related option for DML
accesses to a table or view. This statement can also be used as an embedded SQL
compiler directive.
CONTROL TABLE is an SQL/MX extension.
table
is the name of the table or view to which the control option applies. You must
specify the name with the same qualification as the name that appears in
subsequent references to which the control option applies. For example, if you
specify a fully qualified table name, the fully qualified name must appear in
subsequent references.
*
specifies that the control option applies to all tables subsequently referenced in the
current process. A CONTROL TABLE table statement overrides the effect of a
CONTROL TABLE * statement for the specified table or view.
MDAM {'ENABLE'|'ON'|'OFF'}
specifies whether to use MDAM for subsequently compiled DML statements that
access the index. table refers to the index for which you wish to force MDAM. If
you use the table name instead of the index name, NonStop SQL/MX uses the
table clustering key and no other keys are forced for MDAM.
ENABLE
directs NonStop SQL/MX to determine whether to use MDAM for the specified
index. The default is ENABLE.
ON
directs NonStop SQL/MX to use MDAM.
CONTROL TABLE {table | *} control-table-option
control-table-option is:
MDAM {'ENABLE'|'ON'|'OFF'}
| PRIORITY 'priority-value'
| IF_LOCKED {'RETURN'|'WAIT'}
| TABLELOCK {'ENABLE'|'ON'|'OFF'}
| TIMEOUT 'timeout-value'
| SIMILARITY_CHECK {'ON'|'OFF'}
| RESET