Guy Smith-Ferrier

ADO.NET's SqlClient data provider for SQL Server supports connection pooling, which is enabled by default. It works well: when a connection is closed it is returned to the pool and reused later when another connection using the same connection string and context is created. The result is improved performance. I could delve into the vagaries of how we can test this and what connection string parameters exist to control the connection pooling process, but that isn't what this article is about. This article answers two frequently asked questions about SqlClient connection pooling: How can I set the connection pool timeout, and how can I flush the connection pool? The short answer to both of these questions is that you can't. Of course, that would make for a very short artic... (more)

On Connection Pooling

Guy Smith-Ferrier's article, "SqlClient Connection Pooling Exposed" (.NETDJ, Vol. 1, issue 12, www.sys-con.com/dotnet/article.cfm?ID=483), generated a question from reader Angel Saenz-Badillos. Most Interesting Pooling Article I Have Seen This has to be the most interesting article on managed pooling I have seen. I like the fact that you not only show the solution but warn people that mod... (more)