Connection Pooling and Enterprise Library

Topics: Data Access Application Block
Apr 2, 2010 at 12:54 PM

How does Enterprise Library manage Connection Pooling in DAAB

Apr 5, 2010 at 8:59 AM

For what I know, connection pooling is enabled by default in EntLib DAAB. From my understanding, same from the basic definition of connection pooling. If the DAAB close a connection, by default it won't really be closed by the provider - instead it will be returned to the pool. So whenever a new connection requests come in, it first checks if the pool contains any unused connections and returns one if available. If all connections currently in the pool are busy and the maximum pool size has not been reached, the new connection is created and added to the pool. By having connection pooling enabled this can improve the response time of your application and it prevents the overhead of creating a connection each time you need to access your data store.

Hope this helps,