SQL Server Connection pool limit?

  • Thread starter Thread starter Valerie Hough
  • Start date Start date
V

Valerie Hough

If I'm using connection pooling in my application, is there some way I can
tell if there are no more connections available? Can I control the number?
Are there performance implications ?

Thanks in advance.
Valerie Hough
 
Valerie,

By default, I believe the pool size is 100. If the limit is reached, then
your request gets queued until a connection is available. The performance
implications, the obvious one anyways, would be the delay during the queue
period.

You can control the pool size number in your connection string, use the Max
Pool Size property.

HTH
Altaf
 
It's worth to note that it's likely caused in most cases by unreleased
connections. You may want to double check this is not caused by your
application before solving the problem by increasing this value...
 
Yes. You can use the Performance Counters exposed by the .NET Framework.
However, these are not particularly reliable. They are replaced by new
counters in 2.0. Can you control the number? Understand that a heavily used
site consumes about 20-50 connections. If 100 is not enough you have a
problem. Sure, there are performance implications--each live connection
consumes CPU resources and limits the overall number of connections the
server can support.

--
____________________________________
William (Bill) Vaughn
Author, Mentor, Consultant
Microsoft MVP
INETA Speaker
www.betav.com/blog/billva
www.betav.com
Please reply only to the newsgroup so that others can benefit.
This posting is provided "AS IS" with no warranties, and confers no rights.
__________________________________
 
Back
Top