|
|
|
How many users can connect to access? |
|---|
| message from Guy Cohen on 11 May 2004 |
Hi all,
In the past I wrote a program that served 4 persons.
The client wants to use the program all over the company... 10*X users.
If (users<=this) then
access is still ok
Else
Use SQL server
End if
TIA
Guy
|
| Kevin3NF replied to Guy Cohen on 11 May 2004 |
Depends on how well the app is written in terms of locking, indexes, etc.
Max technical limit is 255 per Microsoft, but I've never heard of one with
that many users. Never seen mor than about 50.. 10-20 is when people
generally start reporting trouble.
One of my fellow posters will tell you that a poorly designed app will crash
with 1 or 2. :-)
|
| Tony Toews replied to Kevin3NF on 11 May 2004 |
Whereas I have a client with 25 users running quite smoothly.
Tony
|
| Kevin3NF replied to Tony Toews on 11 May 2004 |
Yeah...but your databases are designed correctly :-)
|
| Tony Toews replied to Kevin3NF on 11 May 2004 |
1) It has 150 tables
2) One of my mottos is "When in doubt add more tables"
Tony
|
| Kevin3NF replied to Tony Toews on 11 May 2004 |
OK...you're scaring me
|
| Tony Toews replied to Kevin3NF on 11 May 2004 |
Which one scares you? The 150 table BE? Currently at about 300 Mb?
One table of 600k records, 3 or 4 others at 200k to 400k records each?
Or the motto? <smile>
Tony
|
| =?Utf-8?B?U0NITllERVM=?= replied to Kevin3NF on 11 May 2004 |
Was just gonna say, I'm running fine with nearly 50 users, subforms and reports, and nearly 30000 records. But don't get me wrong, let's just say "Database.be.mdb is an unrecognized file format" <compacts and repairs> a few times before I had the time to really streamline it
|
| Guy Cohen replied to Kevin3NF on 11 May 2004 |
If there are currently 4 and they want to expand the usage to all the
company:
=>Conclusion: Program = not (a poorly designed app will crash with 1 or 2)
How many hours should I expect it to take to make it run in SQL server?
I need help with pricing.... :)
TIA
Guy
"Kevin3NF" <KHill@NopeIDontNeedNoSPAM3NF-inc.com> כתב בהודעה
news:%23y5Rcu4NEHA.1388@TK2MSFTNGP09.phx.gbl...
|
| Kevin3NF replied to Guy Cohen on 11 May 2004 |
Select Case FEType
Case '.MDB'
Time = 'small' as Duration
Case '.ADP'
Time = 'longer' as Duration
End Select
If the existing program is one table, one form and one report, I can do it
on my break. If it has hundreds of tables, functions, modules, etc. start
thinking in ters of months. See the above select for a whole new layer of
complexity (ADP)
|
| MacDermott replied to Guy Cohen on 11 May 2004 |
If the program is poorly designed in the first place,
I'm not sure that moving to SQL Server is going to help a whole lot.
Another major issue is how much concurrency you're going to have.
For example, a timesheet program will probably have heavy use in the early
morning and late afternoon, but little in between.
An accounting program may have heavy usage throughout the day, but it won't
have the peaks the timesheet will.
It's the peaks you need to look out for.
I had an Access app which had 100 users logged in simultaneously.
Not especially well designed, either.
But it was a call center; the users spent most of their time on the phone,
and each one used the database directly only a small portion of the time.
HTH
- Turtle
"Guy Cohen" <support@mcam2u.com> wrote in message
news:ukgEo24NEHA.1348@TK2MSFTNGP12.phx.gbl...
|
| Guy Cohen replied to MacDermott on 12 May 2004 |
Thank you Sir/Madam?
Your answer was the best (for me) :)
My case is also a call center with tables for customers, contacts,calls,
meetings and notes.
TY
Guy
"MacDermott" <macdermott@NoSpam.com> כתב בהודעה
news:Ox5ARd8NEHA.1272@tk2msftngp13.phx.gbl...
|
| Arvin Meyer replied to Guy Cohen on 12 May 2004 |
Your biggest problem will be memo fields. Since they are not stored in the
table (a pointer to them is stored in the table) it is easier to corrupt a
database table with a memo field it the database has unstable networks or
careless users. If you can use 255 character text fields, definitely do
that.
Very stable networks and well trained users (those who do do not turn off
machines) and UPSs on each machine are important. I have 2 large databases
used by up to 42 users on 1 and 35 on the other, without any problems
whatsoever. Both of them have memo fields, but very stable networks. The one
I work in mostly has Dell servers, IntelPro network cards and Cisco routers
and switches.
|
| MacDermott replied to Arvin Meyer on 12 May 2004 |
Amen to that!
Almost the only problems I had on that 100-user database hinged on memo
fields.
I always suspected a few dirty NICs of causing some problems, too -
but it didn't seem to be associated with the number of concurrent users.
- Turtle
"Arvin Meyer" <a@m.com> wrote in message
news:euSVXwAOEHA.1340@TK2MSFTNGP12.phx.gbl...
|
|
