Posted by Erland Sommarskog on 07/27/06 10:39

bjorn.augestad@gmail.com (bjorn.augestad@gmail.com) writes:
> I just sampled all statements for one hour, and we had ~450.000 calls
> to sp_reset_connection, or 125 calls per second. Seems way too high to
> me, even if the documentation describes it as lightweight.

Al least connection pooling is working!

> I guess we'll continue to rewrite the clients to use just one
> connection wherever possible. The changes made so far has improved the
> situation a lot. :-)

Yes, with that connection rate, he disconnected model is not very good.
Connection pooling is particular useful in things like web applications,
when you have many users that connect through the same middleware (the
web server), and that run queries very infrequently.

The model is usually fine for Windows applications too. But if you have some
service-type of thing which does not have to wait for a user that goes for a
coffee, it may be better to stay connected.


--
Erland Sommarskog, SQL Server MVP, esquel@sommarskog.se

Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/prodtechnol/sql/2005/downloads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodinfo/previousversions/books.mspx

[Back to original message]