Posted on 2009-02-16
We've been having some SQL Server connection issues and one of our Active Directory admins suggested using connection pooling (we get a lot of timeout expired errors when connecting to any SQL Server 2005, we have 4). I'm a programmer, and my .Net applications use this by default with ADO.Net (I've ran tests to verify this). However, we also have ODBC reports that are run on an application server, and I believe they're pooling but I don't know for sure. Also, I've checked the open connections on the server via both a netstat and running an sp_who2 query and I haven't seen an extraordinary amount of connections open.
1.) Is there anything that needs to be done on the server to enable connection pooling?
2.) Do the microsoft ODBC drivers behave like the ADO drivers and enable pooling by default (if not, can they be enabled/how)?