5, 8 or 25 concurents workloads ?

Hello,
I'm usng MSDE2000A (not MSDE2000)
The MSDE2000 documentation speak about 5 concurents
operations limitation.
The "Approriate uses of MSDE Faq" speak about 25
concurents users (means concurents operations?)
http://www.microsoft.com/sql/msde/howtobuy/msdeuse.asp
(see the "Can I use MSDE as a database for Web
applications?" question)
The SQL Server 2000 Workload Governor speak about 8
concurents operations
http://www.microsoft.com/sql/msde/howtobuy/msdeuse.asp
Who's right? What's the exact number limitation for
MSDE2000A? 8 or 5 or 25 ?
Thanks for reply.
Georges
Thanks for posting this question...
I was myself confused after reading all this.. but after clarification from many posts out here, it seems that the workload governer kicks in after 5 concurrent operations (3 are reserved for the system, so total is 8)..
But the verdict of the people using MSDE is that it seems to work fairly well even if the number of concurrent operations goes till 25 and above.. you'll just have to test you system.
Hope it helps.
dev
"Georges" wrote:

> Hello,
> I'm usng MSDE2000A (not MSDE2000)
> The MSDE2000 documentation speak about 5 concurents
> operations limitation.
> The "Approriate uses of MSDE Faq" speak about 25
> concurents users (means concurents operations?)
> http://www.microsoft.com/sql/msde/howtobuy/msdeuse.asp
> (see the "Can I use MSDE as a database for Web
> applications?" question)
> The SQL Server 2000 Workload Governor speak about 8
> concurents operations
> http://www.microsoft.com/sql/msde/howtobuy/msdeuse.asp
> Who's right? What's the exact number limitation for
> MSDE2000A? 8 or 5 or 25 ?
> Thanks for reply.
> Georges
>
|||The governor is intended to kick in when there are 5 concurrent *USER*
workloads (a workload is NOT the same concept as a user/connection).
The 8 that you see referenced is because there are 3 workloads allotted for
system activity (designed so that the system can continue to do work even if
5 workloads are tying up the system).
The 25 that you see referenced is 25 concurrent users, not concurrent
workloads. Even with 25 users connected to the database, it is unlikely ,
unless you have really inefficient queries (in which case you probably won't
notice the governor anyway). As dev_kh stated, you'll have to test your
system to see if (a) the governor kicks in at all, and (b) whether its
effect is tolerable.
http://msdn.microsoft.com/library/en...r_sa2_0ciq.asp
All of this confusion is one of the primary reasons the governor was removed
in SQL Server 2005 Express, I think.
http://www.aspfaq.com/
(Reverse address to reply.)
"Georges" <anonymous@.discussions.microsoft.com> wrote in message
news:133701c46f12$14ae53c0$a501280a@.phx.gbl...
> Hello,
> I'm usng MSDE2000A (not MSDE2000)
> The MSDE2000 documentation speak about 5 concurents
> operations limitation.
> The "Approriate uses of MSDE Faq" speak about 25
> concurents users (means concurents operations?)
> http://www.microsoft.com/sql/msde/howtobuy/msdeuse.asp
> (see the "Can I use MSDE as a database for Web
> applications?" question)
> The SQL Server 2000 Workload Governor speak about 8
> concurents operations
> http://www.microsoft.com/sql/msde/howtobuy/msdeuse.asp
> Who's right? What's the exact number limitation for
> MSDE2000A? 8 or 5 or 25 ?
> Thanks for reply.
> Georges
|||I thought that MSDE had a limit of 10 concurrent users? Is it 25?
"Aaron [SQL Server MVP]" <ten.xoc@.dnartreb.noraa> wrote in message
news:%23q8AjzybEHA.2660@.TK2MSFTNGP12.phx.gbl...
> The governor is intended to kick in when there are 5 concurrent *USER*
> workloads (a workload is NOT the same concept as a user/connection).
> The 8 that you see referenced is because there are 3 workloads allotted
for
> system activity (designed so that the system can continue to do work even
if
> 5 workloads are tying up the system).
> The 25 that you see referenced is 25 concurrent users, not concurrent
> workloads. Even with 25 users connected to the database, it is unlikely ,
> unless you have really inefficient queries (in which case you probably
won't
> notice the governor anyway). As dev_kh stated, you'll have to test your
> system to see if (a) the governor kicks in at all, and (b) whether its
> effect is tolerable.
> http://msdn.microsoft.com/library/en...r_sa2_0ciq.asp
> All of this confusion is one of the primary reasons the governor was
removed
> in SQL Server 2005 Express, I think.
> --
> http://www.aspfaq.com/
> (Reverse address to reply.)
>
>
> "Georges" <anonymous@.discussions.microsoft.com> wrote in message
> news:133701c46f12$14ae53c0$a501280a@.phx.gbl...
>
|||> I thought that MSDE had a limit of 10 concurrent users? Is it 25?
No, it is neither. As I tried to explain, MSDE doesn't have a limit on
concurrent users at all (not 5, not 8, not 10, not 25, not 5000). There is
a governor that throttles performance at or around 5 simultaneous workloads,
which is *NOT* the same as a connection.
The 25 was a *suggestion* on one of the product pages, for how many
concurrent users a typical system running MSDE could support. This could be
completely different from project to project, as hardware, application code,
usage, bandwidth, database design etc. can differ, and all of these things
impact how an application performs. So you will need to test it out to see
how many simultaneous users and/or workloads your specific scenario can
support.
To provide an analogy for the difference between a concurrent user and a
concurrent workload. Imagine yourself at the DMV, and there are 40 people
waiting around, not doing much. Two people are at the registration counter,
and one person is getting her picture taken for a new drivers' license. The
40 people are "concurrent users" and the other three are "concurrent
workloads" - since they're the only ones actually doing anything productive.
http://www.aspfaq.com/
(Reverse address to reply.)
|||ahhh - thanks!
love the DMV analogy, btw :-)
"Aaron [SQL Server MVP]" <ten.xoc@.dnartreb.noraa> wrote in message
news:%23Bqzmw%23bEHA.1144@.TK2MSFTNGP11.phx.gbl...
> No, it is neither. As I tried to explain, MSDE doesn't have a limit on
> concurrent users at all (not 5, not 8, not 10, not 25, not 5000). There
is
> a governor that throttles performance at or around 5 simultaneous
workloads,
> which is *NOT* the same as a connection.
> The 25 was a *suggestion* on one of the product pages, for how many
> concurrent users a typical system running MSDE could support. This could
be
> completely different from project to project, as hardware, application
code,
> usage, bandwidth, database design etc. can differ, and all of these things
> impact how an application performs. So you will need to test it out to
see
> how many simultaneous users and/or workloads your specific scenario can
> support.
> To provide an analogy for the difference between a concurrent user and a
> concurrent workload. Imagine yourself at the DMV, and there are 40 people
> waiting around, not doing much. Two people are at the registration
counter,
> and one person is getting her picture taken for a new drivers' license.
The
> 40 people are "concurrent users" and the other three are "concurrent
> workloads" - since they're the only ones actually doing anything
productive.
> --
> http://www.aspfaq.com/
> (Reverse address to reply.)
>
|||> love the DMV analogy, btw :-)
Yeah, I was hoping you were in the US; most others wouldn't get it. ;-)
http://www.aspfaq.com/
(Reverse address to reply.)
|||> most others wouldn't get it. ;-)
Just to be clear, I don't mean the concept (I think it's pretty clear even
if you replace DMV with McDonald's or the tax office or your human resources
department).
I mean the irony of talking about the DMV in terms of performance and
workload governing. Most of the locations I have been to have an unlimited
concurrent user threshold, but the staff has a concurrent workload limit of
exactly 1. ;-)
A