I am running an ASP page that opens an ADO connection to an MS SQL database. It starts up a transaction and then executes a series of statements (no SELECTs, only DELETEs and INSERTs). It seems that ...
If you are using identity impersonation (on your web app) and Integrated security (on SQL server), then you will get a seperate connection pool for each user, each with a low number of connections ...