Dec 19, 2000
Don't Cache ADO Database Connections in the ASP Application Object
If you do, then all the pages will fight for the use of this connection. In addition, don't cache an ADO connection in the Session object. If you do, a database connection will be created for every user, defeating connection pooling and overusing server resources. Instead, ADO connections should be created and destroyed on every ASP page that needs to use ADO. This permits connection pooling and ensures all connections are efficiently created and destroyed.