Enables use of ODBC 3.0 connection pooling. When a connection is closed, the Driver Manager actually keeps it alive for a timeout period, and saves the overhead of re-establishing a connection from scratch if the application re-opens an identical connection. ODBC allows you to choose between having a pooling for an ODBC environment or for each driver. See your ODBC documentation for details.
This option is only useful for applications that frequently open and close connections. Note that some environments, such as Microsoft Transaction Server (MTS), control connection pooling themselves. This option will probably improve the performance of ISAPI applications that are not running under MTS.
Syntax:
CONNECTIONPOOL={DRIVER | ENVIRONMENT | NONE}
Properties:
| Default: |
CONNECTIONPOOL=NONE. |
Scope:
| Used at compile time:
|
No
|
| Behavior at run time:
|
Process
|
See
Scope - OpenESQL SQL Compiler Directive Options for more information.
