Hi folks, I'm trying to come up with a scalable connection pooling strategy. I know that .NET has connection pooling built in to the SqlConnection and OleDBConnection objects, but I'm not sure exactly how it works. The documentation says if the same connection string is used, the same pool is used; but I am unclear on what the scope of this is. In other words, if I use the same connection string throughout my entire application, is it using one pool, or do I have to be using the same connection string within a class or within a namespace? It seems like if it is only within a class (or a particular instance of a class) we would end up with a whole lot of pools. When I used to work with Java App Servers, the connection pool was managed on an application-wide basis, but of course I don't know if .NET is the same.
For enterprise applications is there an advantage to having multiple pools (i.e. one used by each module) as opposed to one pool shared within an entire application? Thanks in advance... I'm still learning the architecture side of the fence. Anye __________________________________________________ Do You Yahoo!? Yahoo! Health - your guide to health and wellness http://health.yahoo.com You can read messages from the DOTNET archive, unsubscribe from DOTNET, or subscribe to other DevelopMentor lists at http://discuss.develop.com.
