OpenEdge Data Management: DataServer for Microsoft SQL Server

Chapter 4: Additional Features to Enhance DataServer Performance
Considerations when using ODBC connection pooling and DataServer
connection management
When both ODBC connection pooling and DataServer connection management are
enabled, set the number of managed connections to a value that covers the required
number of connections for a typical application. Reuse of the managed connections
takes precedence over ODBC connection pool connections. The ODBC connection
pool is then an overflow handler for connections required beyond the capacity of the
managed connections. This configuration ensures that there is little risk of having a
negative impact on performance by downgrading to a Fast Forward-Only server-side
cursor in the mainline transaction-oriented connection. For more information on
monitoring the performance of your connection pool, see the “Monitoring cursor and
connection use” section on page 165.
ODBC Connection Pooling
ODBC connection pooling is managed by the ODBC driver manager, external to the
DataServer. The size of the pool grows and contracts dynamically based on demand
and time-out intervals. The upper limit to the pool size is limited only by memory and
other server resource constraints. The DataServer retrieves connections out of the
externally managed pool. ODBC connection pooling is maintained with the
CONNECTION_POOLING option to the -Dsrv connection parameter. ODBC connection
pooling is enabled by default.
Disable ODBC connection pooling with the following syntax:
Syntax
-Dsrv CONNECTION_POOLING,0
Note: To take advantage of ODBC connection pooling in the DataServer, you must
rebuild your schema holder. However, if your schema holder was built before
OpenEdge Version 10.0B, contact Technical Support for information about
how to proceed.
162 OpenEdge Data Management: DataServer for Microsoft SQL Server