Provides a performance enhancement when accessing DB2 common server databases or DRDA databases. This option combines the
SQL PREPARE statement flow with the associated OPEN, DESCRIBE, or EXECUTE statement flow to minimize inter-process or network
flow.
Syntax:
DEFERRED_PREPARE={NO | YES | ALL}
NODEFERRED_PREPARE
Parameters:
| NO |
The PREPARE statement will be executed at the time it is issued. |
| YES |
Execution of the PREPARE statement will be deferred until the corresponding OPEN, DESCRIBE, or EXECUTE statement is issued.
The PREPARE statement will not be deferred if it uses the INTO clause, which requires an SQLDA to be returned immediately.
However, if the PREPARE INTO statement is issued for a cursor that does not use any parameter markers, the processing will
be optimized by pre-OPENing the cursor when the PREPARE is executed.
|
| ALL |
Same as YES, except that a PREPARE INTO statement which contains parameter markers is deferred. If a PREPARE INTO statement
does not contain parameter markers, pre-OPENing of the cursor will still be performed. If the PREPARE statement uses the INTO
clause to return an SQLDA, the application must not reference the content of this SQLDA until the OPEN, DESCRIBE, or EXECUTE
statement is issued and returned.
|
Properties:
| Default: |
NODEFERRED_PREPARE |