And, BTW, this is an oversimplification. Most queries take a tiny fraction
of a second. So you could really support quite a bit more than I show. But
"Hal Berenson" <hberenson@predictableit.com> wrote in message
news:u9qGL4x2FHA.632@TK2MSFTNGP10.phx.gbl...
> The confusion comes from "concurrent queries" versus "concurrent users".
> The workload governor operates off the former while users are typically
> looking to configure based on the latter.
>
> The workload governor allows essentially 480 (sub-second) database queries
> or other (e.g., update) operations per minute without degradation. You
> can ballpark what this means in terms of transactions. Assume a simple
> transaction has perhaps 5 queries. A mid-level has perhaps 20, and a
> complex transaction has about 40. So you can support between 10 and 100
> transactions per minute with MSDE with no degradation. OLTP leans towards
> the simple side (volume-wise you might have 70-80% of your transactions in
> the simple category) so lets assume 75 transactions per minute.
>
> The real question for MSDE thus is, how many users does it take to
> generate 75 transactions in a minute. If your users submit one
> transaction per minute then you could support 75 users. If your users
> submit 2-3 transactions per minute then you get to the 25 users that
> Microsoft targets as a maximum. If your workload leans towards the more
> complex transactions then the numbers you support go down. If users do
> very infrequent transactions then the numbers go up.
>
> Microsoft's real target for MSDE was for apps that support 10 users or
> less. There is a lot of history there in terms of the business target and
> the technical requirements. One part of the requirements analysis
> dictated that hard concurrent user limits cause major customer
> dissatisfaction. So MSDE was not given a hard concurrent user limit nor
> was the governor set to make performance fall off a cliff after 10 users.
> The result is that for many applications MSDE supports far larger numbers
> of users than the technical specs might indicate.
>
> Hal Berenson, President
> PredictableIT, LLC
>
www.predictableit.com >
>
>
> "Andrea Montanari" <andrea.sqlDMO@virgilio.it> wrote in message
> news:3sbpn3Fn11hqU1@individual.net...
>> hi Andrew,
>> Andrew @ Abaki wrote:
>>> Hi All. A friend of mine mentioned that Release A actually has the
>>> max number of concurrent queries to be 25 instead of 7 as MSDE. Is
>>> this true? Thank you
>>
>> false.. MSDE (and there's only one of it, only different packages with
>> different eulas) allows up to 8 concurrent (of the ones included in the
>> count of the Governor it self) batches before the Governor Workload
>> kicking in ...
>>
http://msdn.microsoft.com/library/?url=/library/en-us/architec/8_ar_sa2_0ciq.asp?frame=true
>>
>> 25 is a "magic number" guessed by Microsoft,
>>
http://www.microsoft.com/sql/msde/howtobuy/msdeuse.mspx, at the question
>> Q. Can I use MSDE as a database for Web applications?
>> A. Yes, MSDE is an ideal solution for basic Web applications with up to
>> 25 concurrent users.
>>
>> this number obviously depends on the application code quality, access
>> type, data nature and design, activities on it, ....
>> --
>> Andrea Montanari (Microsoft MVP - SQL Server)
>>
http://www.asql.biz/DbaMgr.shtm http://italy.mvps.org >> DbaMgr2k ver 0.15.0 - DbaMgr ver 0.60.0
>> (my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
>> interface)
>> --------- remove DMO to reply
>>
>
>