Hi all,

when in a web situation...when a user request for data from db..they would open the connection then close it...this would cost a lot of io....connection pooling is opening a certain no of connection when the user finish their process instead of closing the connection they would return the connection back to the pool for other users, maintaining an idle connection cost less io....but current solutions uses the database to control these settings...

any sample of how to use an independent program to queue up the request to reduce the workload on the database

thanks :)

The database doesn't manage connection pooling - ADO.NET does: http://msdn.microsoft.com/en-us/library/aa175863(SQL.80).aspx

HI,

Is that any way to use independent program to queue the connection to avoid the connection overflow, for each time the user connect the database simultaneously, instead of using the ADO.NET?

Thanks

;)

Not that I am aware of.