|
|
You're in the
sql server msde
group:MSDE limits?
sql server msde:
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
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! [quoted text, click to view] 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... [quoted text, click to view] > 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
2 GB is max for MSDE.
Lars Broberg Elbe-Data AB http://www.elbe-data.se Remove "nothing." when replying to private e-mail! [quoted text, click to view] 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... > >>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 > >
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 [quoted text, click to view] "Lars Broberg" <lars.b@elbe-data.nothing.se> wrote in message news:u4hwQweMFHA.1476@TK2MSFTNGP09.phx.gbl... > 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
[quoted text, click to view]
"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
[quoted text, click to view]
"Andrea Montanari" <andrea.sqlDMO@virgilio.it> wrote in message news:3atbhaF6fc386U1@individual.net... > 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 :) That's all I was looking for. Thanks! [quoted text, click to view] >> 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/?url=/library/en-us/architec/8_ar_sa2_0ciq.asp?frame=true Thanks for the link. That will help tremendously, I think. Matt
hi,
[quoted text, click to view] 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 :) [quoted text, click to view] > > 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 [quoted text, click to view] > 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/?url=/library/en-us/architec/8_ar_sa2_0ciq.asp?frame=true -- Andrea Montanari (Microsoft MVP - SQL Server) http://www.asql.biz/DbaMgr.shtm http://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
excellent thread, I have learnt more about MSDE 2000 in this conversation
than a week of research. Could I trouble you to answer the same question for MSDE 2005 (or SQL 2005 Express edition i think they are calling it) i.e what limits does it have ? Thanks for your time. Scott
ie
RUNS ON: -2003 -2000 -XP LIMITS ARE: - NO DTS - 1CPU - 4 GB data - 1 GB Ram - No workload throttle (i think this means that its unlimited unlike MSDE 2000 "8" workload processing restriction) cheers scott
thanks for reply.
- is there a release date for Express 2005 yet ? - "it can't be a merge replication publisher" what is this function actually for ? - what is the "subscriber" function for ? - what does the "SQL Agent" do ? (i.e send emails etc....) sorry for all the questions - would clear a few things up for me though. Scott
Yes to all in the list plus it can't be a merge replication publisher, but
it can be a subscriber. And there's no SQL Agent. HTH, -- Greg Low [MVP] MSDE Manager SQL Tools www.whitebearconsulting.com [quoted text, click to view] "scott" <nospamscott@yahoo.com> wrote in message news:OyJxsqdOFHA.2788@TK2MSFTNGP09.phx.gbl... > ie > > RUNS ON: > -2003 > -2000 > -XP > > LIMITS ARE: > - NO DTS > - 1CPU > - 4 GB data > - 1 GB Ram > - No workload throttle (i think this means that its unlimited unlike MSDE > 2000 "8" workload processing restriction) > > cheers > scott > >
Hi Scott,
Comments inline: HTH, -- Greg Low [MVP] MSDE Manager SQL Tools www.whitebearconsulting.com [quoted text, click to view] "scott" <nospamscott@yahoo.com> wrote in message GREG> No, it'll likely be with SQL Server 2005 in the last few months of news:%2361eV6eOFHA.904@tk2msftngp13.phx.gbl... > thanks for reply. > > - is there a release date for Express 2005 yet ? this year. [quoted text, click to view] > - "it can't be a merge replication publisher" what is this function GREG> Merge replication allows you to have the same table able to be updated > actually for ? on different MSDE servers at the same time. The servers can be temporarily disconnected if necessary and they resync when reconnected. There is conflict resolution. One server is used to define the tables to be "published". [quoted text, click to view] > - what is the "subscriber" function for ? GREG> The other server(s) that can also use the table.[quoted text, click to view] > - what does the "SQL Agent" do ? (i.e send emails etc....) GREG> Understands jobs, tasks, operators (Agent's own concept not server > logins or database users), schedules and alert processing. [quoted text, click to view] > sorry for all the questions - would clear a few things up for me though. GREG> No problems - ask away> Scott >
got back today and saw your response, just wanted to post a quick thank you.
Cheers Scott
Don't see what you're looking for? Try a search.
|
June 2004
July 2004
August 2004
September 2004
October 2004
November 2004
December 2004
January 2005
February 2005
March 2005
April 2005
May 2005
June 2005
July 2005
August 2005
September 2005
October 2005
November 2005
December 2005
January 2006
February 2006
March 2006
April 2006
May 2006
June 2006
July 2006
August 2006
September 2006
October 2006
November 2006
December 2006
January 2007
February 2007
March 2007
April 2007
May 2007
June 2007
July 2007
August 2007
September 2007
October 2007
| home · blog · groups | Questions? Comments? Contact the dn |