Purpose of connection pooling in ADO.NET

It's a technique to allow multiple clinets to make use of a cached set of shared and reusable connection objects providing access to a database.

Opening/Closing database connections is an expensive process and hence connection pools improve the performance of execution of commands on a database for which we maintain connection objects in the pool. It facilitates reuse of the same connection object to serve a number of client requests. Every time a client request is received, the pool is searched for an available connection object and it's highly likely that it gets a free connection object.
Otherwise, either the incoming requests are queued or a new connection object is created and added to the pool (depending upon how many connections are already there in the pool and how many the particular implementation and configuration can support).
As soon as a request finishes using a connection object, the object is given back to the pool from where it's assigned to one of the queued requests (based on what scheduling algorithm the particular connection pool implementation follows for serving queued requests). Since most of the requests are served using existing connection objects only so the connection pooling approach brings down the average time required for the users to wait for establishing the connection to the database.

Check this to know how to do connection pooling,
http://www.codeproject.com/Articles/17768/ADO-NET-Connection-Pooling-at-a-Glance

2 Replies

Know the answer? Post it — somebody with the same question will find it here.

Satyapriya Nayak14y ago
Hi sharad, Please refer the below links, http://www.c-sharpcorner.com/uploadfile/mahesh/understanding-connection-pooling-in-ado-net/default.aspx, http://www.c-sharpcorner.com/uploadfile/4d56e1/connection-pooling-ado-net/default.aspx, http://www.c-sharpcorner.com/UploadFile/dsdaf/ConnPooling07262006093645AM/ConnPooling.aspx, http://www.c-sharpcorner.com/UploadFile/munnamax/connectionpooling08112007062332AM/connectionpooling.aspx, Thanks
Santhosh Kumar Jayaraman14y ago
It's a technique to allow multiple clinets to make use of a cached set of shared and reusable connection objects providing access to a database.

Opening/Closing database connections is an expensive process and hence connection pools improve the performance of execution of commands on a database for which we maintain connection objects in the pool. It facilitates reuse of the same connection object to serve a number of client requests. Every time a client request is received, the pool is searched for an available connection object and it's highly likely that it gets a free connection object.
Otherwise, either the incoming requests are queued or a new connection object is created and added to the pool (depending upon how many connections are already there in the pool and how many the particular implementation and configuration can support).
As soon as a request finishes using a connection object, the object is given back to the pool from where it's assigned to one of the queued requests (based on what scheduling algorithm the particular connection pool implementation follows for serving queued requests). Since most of the requests are served using existing connection objects only so the connection pooling approach brings down the average time required for the users to wait for establishing the connection to the database.

Check this to know how to do connection pooling,
http://www.codeproject.com/Articles/17768/ADO-NET-Connection-Pooling-at-a-Glance