Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss
...application can reuse that connection...
1 view
Skip to first unread message
byungsoo
Nov 11, 1999, 3:00:00 AM11/11/99
to
MSDN says
'ODBC connection pooling is a feature that is implemented by the ODBC
Driver Manager. Connection pooling makes it much cheaper for an application
to open and close a database connection. Once a connection has been created
and placed in a connection pool, an application can reuse that connection
without paying the cost of opening a new database connection'.
'ODBC connection pooling is a feature that is implemented by the ODBC
Driver Manager. Connection pooling makes it much cheaper for an application
to open and close a database connection. Once a connection has been created
and placed in a connection pool, an application can reuse that connection
without paying the cost of opening a new database connection'.
Isn't it interesting? It also says that
'Configuring the ODBC Driver to Support Connection Pooling For the ODBC 3.5
Driver Manager, connection pooling is controlled on a driver by driver basis
through the CPTimeout registry setting. If this registry entry is not
present, connection pooling is disabled. To enable connection pooling for a
specific driver, create the following registry entry:
HKLM\Software\ODBC\ODBCINST.INI\<driver name>\[CPTimeout]
Where CPTimeout is a string-value that specifies the timeout in seconds.'
I wonder how many seconds I'd set it to. I started with 100. It seems
working fine nevertheless I wish to have more specific data. I am working
with IBM AS400/DB2. Any idea? suggestions?
byun...@tsb.co.kr
0 new messages