What is the MSDE number of users limit?

  • Thread starter Thread starter Tomer
  • Start date Start date
T

Tomer

I want to set up a single computer with 2000 pro or XP pro that has MSDE
installed, and perform pull/push operations from several PPCs (that are
connected to client computers), plus connect directly to the MSDE database
from a vb application ( which also can run on several clients ).

Tomer.
 
Thanks everyone. I had the same question

I can have up to 25 people reading and writing and perhaps another 30 just reading
We also go across the wire to MN for 10 of the 25
All our apps are in Access2000, and currently the data is not split from the forms, which I will want to do
We all do have one server that we access
Was wondering about using MSDE as a prelude for (a "sometime" in the future) mssql
Sounds like MSDE won't be great for 25 people. Will have to tune Access asbestos as possible

Michael
 
Michael,

Since the throttling behavior of MSDE depends on concurrent batches rather
than number of users or connections, you really can't tell if MSDE will be
suitable for 25 people without testing. It just depends on how often those
25 people are hitting the database and how long each batch takes. I'd
suggest just trying it, because MSDE does give you the option of scaling up
to SQL Server when you need the horsepower.
--
Ginny Caughey
..Net Compact Framework MVP

Michael said:
Thanks everyone. I had the same question.

I can have up to 25 people reading and writing and perhaps another 30 just reading.
We also go across the wire to MN for 10 of the 25.
All our apps are in Access2000, and currently the data is not split from
Click to expand...
the forms, which I will want to do.
 
In addition, I strongly suggest you check out this article on MSDN by Brian
A. Randell
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnmsde2kwrk/html/msde2000webapp.asp
("Using MSDE 2000 in a Web Application").
Note this passage:
"The key to increasing scalability in an MSDE 2000 application is to reduce
the number of concurrent operations to avoid invoking the Workload Governor.
When the Workload Governor detects more than eight simultaneous operations,
it injects a pause. The more concurrency violations detected, the more
pauses injected by the governor."
The important stuff is done my making adjustments to the default connection
string - by decreasing the Max Pool Size to 5 and increasing Connection
Timeout from 15 to 60 he achieves quite striking improvements in performance
where the number of users is 20 or more.
 
Back
Top