Quote Originally Posted by leinad31 View Post
That is only ONE aspect/purpose of pooling; due to request-response (web) environment where opening and closing connections will take too much time otherwise.

Also, a single username in a client-server environment (just to justify use of pooling) means deployment of credentials with app; not my cup of tea.
That's the point of pooling... the connection isn't actually closed on the server... it remains open, allowing further connections to be established from the client faster.

And pooling doesn't limit you to a single username... you can use it even with specific users... it just means your pooling happens at the user level, rather than the application level.

And while pooling isn't panacea, it isn't a death sentence either. And whther you know it or not, you're using it if you're using SQL Server.

-tg