Connection pooling and authentication

In ODBC, the driver manager controls connection pooling.

An application programmer must be aware of the effects of connection pooling when using authentication. The driver manager does not control when its connections are placed in the pool or when a connection is pulled from the pool. If the application connects and disconnects without the knowledge of the user, the performance benefits of connection pooling are maintained and the user does not receive any unexpected authentication challenges. If the application does make the user aware they are re-establishing a connection, there is still no authentication challenge because the connection between the driver manager and the server was never closed. For more information about connection pooling, see the Microsoft™ Data Access SDK documentation.