13.01.2013 Views

OpenEdge Data Management: DataServer for Microsoft SQL Server

OpenEdge Data Management: DataServer for Microsoft SQL Server

OpenEdge Data Management: DataServer for Microsoft SQL Server

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

Enhancements overview<br />

For installations where the number of ODBC connections is limited, you might decide to<br />

enable only the <strong>Data</strong><strong>Server</strong> connection management. For deployments in which memory<br />

constraints are a concern, enabling only the ODBC connection pool provides on-demand<br />

connections, with optimized resource efficiency. If both an ODBC connection pool and<br />

managed connections coexist in the same <strong>Data</strong><strong>Server</strong> process, the managed connections<br />

will come from the ODBC connection pool. The managed connections are distinguished<br />

from the connection pool connections in that they are never released back to the pool <strong>for</strong><br />

the life of an ABL session.<br />

Considerations when using ODBC connection pooling and <strong>Data</strong><strong>Server</strong><br />

connection management<br />

When both ODBC connection pooling and <strong>Data</strong><strong>Server</strong> connection management are enabled, set<br />

the number of managed connections to a value that covers the required number of connections<br />

<strong>for</strong> a typical application. Reuse of the managed connections takes precedence over ODBC<br />

connection pool connections. The ODBC connection pool is then an overflow handler <strong>for</strong><br />

connections required beyond the capacity of the managed connections. This configuration<br />

ensures that there is little risk of having a negative impact on per<strong>for</strong>mance by downgrading to a<br />

Fast Forward-Only server-side cursor in the mainline transaction-oriented connection. For more<br />

in<strong>for</strong>mation on monitoring the per<strong>for</strong>mance of your connection pool, see the “Monitoring cursor<br />

and connection use” section on page 4–6.<br />

ODBC Connection Pooling<br />

ODBC connection pooling is managed by the ODBC driver manager, external to the<br />

<strong>Data</strong><strong>Server</strong>. The size of the pool grows and contracts dynamically based on demand and<br />

time-out intervals. The upper limit to the pool size is limited only by memory and other server<br />

resource constraints. The <strong>Data</strong><strong>Server</strong> retrieves connections out of the externally managed pool.<br />

ODBC connection pooling is maintained with the CONNECTION_POOLING option to the -Dsrv<br />

connection parameter. ODBC connection pooling is enabled by default.<br />

Disable ODBC connection pooling with the following syntax:<br />

Syntax<br />

-Dsrv CONNECTION_POOLING,0<br />

Note: To take advantage of ODBC connection pooling in the <strong>Data</strong><strong>Server</strong>, you must rebuild<br />

your schema holder. However, if your schema holder was built be<strong>for</strong>e <strong>OpenEdge</strong><br />

Version 10.0B, contact Technical Support <strong>for</strong> in<strong>for</strong>mation about how to proceed.<br />

4–3

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!