Hi,

I am using Asp.net webservice to invoke the connections. In this case does .Net provide connection pooling. I thought the db creates and manages the connection pool.

We are creating the connection string using default values, so connection pooling is true. We use one single connection string , so the connections are for the same string.

Not using a DAL approach might also negate the use of connection pooling...

>> We are using a data access layer approach by having the connection,sql in a separate class

The transactions are committed and disposed. Connections are closed on success (Also rollbacks, connection close on exceptions).

The connections continue in "sleeping" status even after the close. What would cause that? and how is the time configurable - i.e. the time that sqlserver maintains a connection in active status after it is closed by .net ?