ONLY 5 concurrent connections?

Hi all,
Is it true that MSDE can only handle 5 concurrent
connections? I cant seem to find the proof in the
documentation that this is true.
http://forums.msdn.ph/ShowPost.aspx?PostID=39677
HTH, Jens Smeyer.
http.//www.sqlserver2005.de
"chris" <anonymous@.discussions.microsoft.com> schrieb im Newsbeitrag
news:1f0201c54401$463bd6f0$a601280a@.phx.gbl...
> Hi all,
> Is it true that MSDE can only handle 5 concurrent
> connections? I cant seem to find the proof in the
> documentation that this is true.
|||On Mon, 18 Apr 2005 03:27:51 -0700, chris wrote:

>Hi all,
>Is it true that MSDE can only handle 5 concurrent
>connections? I cant seem to find the proof in the
>documentation that this is true.
Hi Chris,
It isn't true.
MSDE imposes no limit on the number of connections. It does impose a
limit on the number of concurrent workloads (i.e. internal threads in a
busy state - usually executing your queries). The limit is set to 8
concurrent workloads, but internal processes take away the first 3,
leaving you with 5 to spend for your goals. If more than 8 workloads are
active at the same time, performance for all workloads is throttled. ANd
the more you exceed the limit, the more the performance will be
throttled.
In a typical data-entry situation, you can easily exceed 20 or even 40
connections - if the data entry screens are complex and the server-side
processing limited, you could even hit 100 connecitons without problems.
On the other hand: if you use complex processing, using a client to
spawn multiple sessions, each executing complex and time-consuming
queries in parallel to each other, then executing the process from just
one computer at a time might already be enough to exceed the limit and
degrade the performance.
http://msdn.microsoft.com/library/?u...asp?frame=true
Best, Hugo
(Remove _NO_ and _SPAM_ to get my e-mail address)
|||And this workload limit is removed in SQL Express (MSDE's replacement).
____________________________________
William (Bill) Vaughn
Author, Mentor, Consultant
Microsoft MVP
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.
__________________________________
"Hugo Kornelis" <hugo@.pe_NO_rFact.in_SPAM_fo> wrote in message
news:0v1861pak4dhf7qhvdlodfno2s4unlqil4@.4ax.com...
> On Mon, 18 Apr 2005 03:27:51 -0700, chris wrote:
>
> Hi Chris,
> It isn't true.
> MSDE imposes no limit on the number of connections. It does impose a
> limit on the number of concurrent workloads (i.e. internal threads in a
> busy state - usually executing your queries). The limit is set to 8
> concurrent workloads, but internal processes take away the first 3,
> leaving you with 5 to spend for your goals. If more than 8 workloads are
> active at the same time, performance for all workloads is throttled. ANd
> the more you exceed the limit, the more the performance will be
> throttled.
> In a typical data-entry situation, you can easily exceed 20 or even 40
> connections - if the data entry screens are complex and the server-side
> processing limited, you could even hit 100 connecitons without problems.
> On the other hand: if you use complex processing, using a client to
> spawn multiple sessions, each executing complex and time-consuming
> queries in parallel to each other, then executing the process from just
> one computer at a time might already be enough to exceed the limit and
> degrade the performance.
> http://msdn.microsoft.com/library/?u...asp?frame=true
> Best, Hugo
> --
> (Remove _NO_ and _SPAM_ to get my e-mail address)