max connections?

Ok, yeah, I'm being lazy...
Any comments?Geseundheit ?

-PatP|||Thank you...Thank you very much...

x002548 has left the building....|||Originally posted by Pat Phelan
Geseundheit ?

-PatP

We will be amused if you can explicate in english...:D in advance.|||Originally posted by Satya
We will be amused if you can explicate in english...:D in advance. There is an enormous amount of rather obscure humor in this thread.

Brett's original post made about as much sense to me as a sneeze. Max connections of what to what? Me to the red head at the bar, max connections equals zero.

I responded with a German word/phrase that is the courteous response to a sneeze. I hoped to provoke a bit more explanation of what Brett meant.

Brett apparently picked my response as a reference to an old Elvis Pressley movie scene. He then carried that reference further.

Like I said, the whole thread is rather obscure. I found it funny, YMMV.

-PatP|||Great... thanks for the meticulous explanation... a part of Friday funnies.:) :D :cool:|||ok...ok...

a server allows connections, yes?

We use connection pooling...you can set the min and max that it will manage...

Is there an upper limit of connections allowed by the server or before performance degrades?

Or am I phrasing this totally wrong?

Is it 5:00 yet?|||Well, its not 17:00 for you, but for me it is... so in jovial mood:p

Then coming to original point :
Max Pool Size keyword is to determine how many connections the pool will hold.

By default, the Data Provider permits 100 connections to accumulate in each pool. This doesn't mean that you start with 100 SqlConnection objects or 100 connections, only that you can't create more than 100 connections per pool.

If you try to exceed the maximum limit you've set, your application will wait until you pass the ConnectionTimeout limit or until a connection becomes available in the pool, then raise an exception. Max Pool Size doesn't limit the number of pools you can createthat limit is determined by the number of SQL Server connections that your sa setting or license makes available (about 32,768 per cluster).|||Originally posted by Brett Kaiser
a server allows connections, yes? If properly configured, yes.
Originally posted by Brett Kaiser
We use connection pooling...you can set the min and max that it will manage...

Is there an upper limit of connections allowed by the server or before performance degrades? Yes. The connection pooling is typically done on the "client" side of the connection, although it can be done on both sides.

In general, you want to have enough "idle" connections to service any resonable load of connection requests. This is usually between 2-5% (rounded up) of your pooled connections idle. This can vary considerably in "spikey" usage situations.

Connection pooling allows near instant initiation of new connections, but it can waste unnecessary resources if misused.
Originally posted by Brett Kaiser
Is it 5:00 yet? Somewhere! Probably about Munich by now.

-PatP