Home > Archive > Visual Basic > January 2006 > MS Access
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
|
|
|
| What is the maximun number of user que an MDB file can handle efficiently?
Where can I find this documentation?
--
Rick
| |
|
| As I understand it there is a limit of concurrent 255 users. That
doesn't apply to the number of users you may store in your mdw
(workgroup) file.
As to how many can be handled efficiently.... I've seen 60 to 80
concurrent connections with no problems but it obviously (hugely)
depends on the nature of your application, your network infrastructure
and your disk(s) speeds. If most users will just be viewing a simple
form and making the occasional update then you could probably hit 255
w/o performance issues. If they're regularly performing complex queries
you might struggle at 10 or 20.
Further it will also be affected on whether you're using an MDE/MDB setup.
Oh and don't forget the 2GB file limit.
I don't know where you can find further documentation but
microsoft.public.access might be a good place to start.
Rick wrote:
> What is the maximun number of user que an MDB file can handle efficiently?
> Where can I find this documentation?
>
| |
|
|
"Rick" <Rick@discussions.microsoft.com> wrote in message
news:29FB6CB0-BBA4-40FF-A822-33E86F0954D2@microsoft.com...
> What is the maximun number of user que an MDB file can handle efficiently?
> Where can I find this documentation?
>
> --
> Rick
Back in the MSAccess 97/Jet 3x days MS published an knowledge-based article
similar to the one below that gave the specific numbers of 18 suggested
concurrent users and 24 as a maximum. I can't find the new location for the
article.
"How to keep a Jet 4.0 database in top working condition"
http://support.microsoft.com/kb/303528/
As you will note MS no longer gives a number, but generally advises against
using MSAccess - "Microsoft Jet is not intended for use with high-stress
server applications, high-concurrency server applications, or 24 hours a
day, seven days a w server applications."
For any given Problem Domain there is likely an optimum 'number', however,
that "number" will depend totally on your application, what your are doing,
how you are doing it, how often you are doing it, and the hardware and wire
you are using. There is NO magic number.
Even when MS was 'suggesting' 18 - I knew of distributed applications that
were supporting 30 or more users with no impact. I also ran across
situations where six was a killer. IMHO, I used 11 as a good max. But even
if you found a 'number' - I doubt it would be accurate for your situation.
hth
-ralph
| |
| Michael D. Ober 2006-01-09, 7:15 pm |
| The rule of thumb I ran across for Access 97 was 80 - 100 users reading the
database, but only 5 updating it. I suspect that Access 2003 will be
similar.
Mike Ober.
"Rick" <Rick@discussions.microsoft.com> wrote in message
news:29FB6CB0-BBA4-40FF-A822-33E86F0954D2@microsoft.com...
> What is the maximun number of user que an MDB file can handle efficiently?
> Where can I find this documentation?
>
> --
> Rick
>
| |
| David J Mark 2006-01-09, 7:16 pm |
| There is no answer for this. A competently-designed Access database can
handle dozens of users at once, depending on how often the app talks to the
db. A poorly designed db (the norm for Access) and/or app will eventually
have problems, regardless of the number of users.
"Rick" <Rick@discussions.microsoft.com> wrote in message
news:29FB6CB0-BBA4-40FF-A822-33E86F0954D2@microsoft.com...
> What is the maximun number of user que an MDB file can handle efficiently?
> Where can I find this documentation?
>
> --
> Rick
|
|
|
|
|