Is there a physical limit to how many simultaneous users MSDE can have. I
have read 25... and i have heard 10... what are the limits?
/Richard
Richard,
Well, there are no fixed limit. The governor will slow down when over 8
concurrent (active) connections. I think SQL Server use 3 itself,
leaving 5 for "your" use. These can handle a lot of users, depending on
how "busy" they are... If you have an app where every user is hitting
the database "all the time" with heavy worklooads, then you are "safe"
with 5 users and probabaly 10 will "work". If your app is using the
server less frequently, 25 users is certainly possible.
So the answer is: It depends... (on your app and your users)
Lars Broberg
Elbe-Data AB
http://www.elbe-data.se
Remove "nothing." when replying to private e-mail!
Richard Bibby wrote:
> Hej,
> Is there a physical limit to how many simultaneous users MSDE can have. I
> have read 25... and i have heard 10... what are the limits?
> /Richard
>
|||ok.. what about database size?
"Lars Broberg" <lars.b@.elbe-data.nothing.se> skrev i meddelandet
news:u4hwQweMFHA.1476@.TK2MSFTNGP09.phx.gbl...[vbcol=seagreen]
> Richard,
> Well, there are no fixed limit. The governor will slow down when over 8
> concurrent (active) connections. I think SQL Server use 3 itself, leaving
> 5 for "your" use. These can handle a lot of users, depending on how "busy"
> they are... If you have an app where every user is hitting the database
> "all the time" with heavy worklooads, then you are "safe" with 5 users and
> probabaly 10 will "work". If your app is using the server less frequently,
> 25 users is certainly possible.
> So the answer is: It depends... (on your app and your users)
> Lars Broberg
> Elbe-Data AB
> http://www.elbe-data.se
> Remove "nothing." when replying to private e-mail!
>
> Richard Bibby wrote:
|||2 GB is max for MSDE.
Lars Broberg
Elbe-Data AB
http://www.elbe-data.se
Remove "nothing." when replying to private e-mail!
Richard Bibby wrote:
> ok.. what about database size?
>
> "Lars Broberg" <lars.b@.elbe-data.nothing.se> skrev i meddelandet
> news:u4hwQweMFHA.1476@.TK2MSFTNGP09.phx.gbl...
>
>
|||The limit is not based upon concurrent connections. It is based upon
concurrent "workloads". There is a big difference. When the system needs to
execute more than 8 concurrent query plans, it inserts a delay in each
logical page access. For small queries, this can have a minor effect. For
larger table scans, this can have a large effect. Use DBCC
CONCURRENCYVIOLATION to investigate if any delays have been inserted and how
often. We have regularly seen more than 20 winform users happy with a single
instance of the MSDE. The 2G database size limit seems to impact most people
before the query governor does.
HTH,
Greg Low [MVP]
MSDE Manager SQL Tools
www.whitebearconsulting.com
"Lars Broberg" <lars.b@.elbe-data.nothing.se> wrote in message
news:u4hwQweMFHA.1476@.TK2MSFTNGP09.phx.gbl...[vbcol=seagreen]
> Richard,
> Well, there are no fixed limit. The governor will slow down when over 8
> concurrent (active) connections. I think SQL Server use 3 itself, leaving
> 5 for "your" use. These can handle a lot of users, depending on how "busy"
> they are... If you have an app where every user is hitting the database
> "all the time" with heavy worklooads, then you are "safe" with 5 users and
> probabaly 10 will "work". If your app is using the server less frequently,
> 25 users is certainly possible.
> So the answer is: It depends... (on your app and your users)
> Lars Broberg
> Elbe-Data AB
> http://www.elbe-data.se
> Remove "nothing." when replying to private e-mail!
>
> Richard Bibby wrote:
|||"Greg Low [MVP]" <greglow@.lowell.com.au> wrote in message
news:%23aRti5rMFHA.3336@.TK2MSFTNGP10.phx.gbl...
> The limit is not based upon concurrent connections. It is based upon
> concurrent "workloads". There is a big difference. When the system needs
> to execute more than 8 concurrent query plans, it inserts a delay in each
> logical page access. For small queries, this can have a minor effect. For
> larger table scans, this can have a large effect. Use DBCC
> CONCURRENCYVIOLATION to investigate if any delays have been inserted and
> how often.
So you are saying that MSDE inserts artificial delays just for the purpose
of slowing itself down because it is not the full version of SQL Server?
I'm just wondering. I had always heard that the only differences were the 2
GB limit and 5 connections...but that more connections were allowed, it
would just wait before letting them do anything until a spot opened up.
Then again, I don't know what I'm talking about.
Is there an easy way to tell if I am going to use more than 8 concurrent
query plans?
Matt
|||hi,
YYZ wrote:
> So you are saying that MSDE inserts artificial delays just for the
> purpose of slowing itself down because it is not the full version of
> SQL Server?
loosely speaking, yes
> I'm just wondering. I had always heard that the only differences
> were the 2 GB limit and 5 connections...but that more connections
> were allowed, it would just wait before letting them do anything
> until a spot opened up.
up to 32767 connections are theoretical valid for MSDE too, but you'll go
out of resources long before that
> Then again, I don't know what I'm talking about.
> Is there an easy way to tell if I am going to use more than 8
> concurrent query plans?
it's not about query plans, but, again, concurrent workloads.. please have a
look at
http://msdn.microsoft.com/library/?u...asp?frame=true
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.11.1 - DbaMgr ver 0.57.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
|||"Andrea Montanari" <andrea.sqlDMO@.virgilio.it> wrote in message
news:3atbhaF6fc386U1@.individual.net...
> hi,
> YYZ wrote:
> loosely speaking, yes
That's all I was looking for. Thanks!
> it's not about query plans, but, again, concurrent workloads.. please have
> a
> look at
> http://msdn.microsoft.com/library/?u...asp?frame=true
Thanks for the link. That will help tremendously, I think.
Matt
No comments:
Post a Comment