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
modifying internal state is not guaranteed to work across releases.
I have been working with Appdomains unloads; these are very important for
applications that host the URT, like the new version of SQL Server, and of
course, IIS has been using this ever since we shipped v1.0.
It is definitely a drastic solution, but it works well as a stopgap measure,
and it would be a version-friendly soluti... (more)
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
str... (more)