In each of the examples we've discussed, we've created a new
object for each session, and then done something with it. However, consider a site where the number of simultaneous users is in the hundreds. In this environment, creating a new Connection
object for each and every user can be very resource intensive. To help alleviate this problem, ADO can take advantage of a new feature provided with ODBC 3.0 and ASP known as connection pooling. This is a resource manager for connections, maintaining the open state on frequently used connections, and thereby avoiding the need to continuously create new connections.Connection