Dustin
|
| Posted: 04/18/2002, 2:39 PM |
|
Right now I'm testing the employee directory module using asp w/ access 2000. It seems a little slow. My hosting account offers asp, cf, perl, and php (my hosting account is cross platform b/t Unix and NT). What language along with which db (access, mysql, sql, etc) would be best??
Thanks, Dustin
|
|
|
|
Brent
|
| Posted: 04/18/2002, 2:49 PM |
|
Such a loaded question. That's like asking 10 people what is the best car?
And you get back 15 different answers.<g>
It all depends what you're trying to accomplish. The problem may be Access
is not fast enough to support a large number of users. Simply changing your
database may solve the problem.
How many people will be accessing the database at one time and how many
records will you have? The more info you give us the better the answer will
be.
|
|
|
|
Dustin
|
| Posted: 04/18/2002, 2:59 PM |
|
Thanks for the quick response. I'm new to all of this :)
We'll probably have no more than 10-15 simultaneous users. We'll probably have approx 300 records or so in the database. Am I correct in assuming that Access should work ok?
Thanks for your help.
|
|
|
|
Peter
|
| Posted: 04/19/2002, 8:10 AM |
|
ASP with Access is fine for what you are doing. -- I have an intranet app running with more that 300 users and the Access DB has now over 2000 records.
Access handles 256 simultaneous users (on the web you are only connected during read and write events) and the DB limit is 1 GigaByte for Access2000 and 2 GB for AccessXP (2002).
|
|
|
|
Brent
|
| Posted: 04/19/2002, 8:13 AM |
|
>We'll probably have no more than 10-15 simultaneous users. We'll probably have approx 300
>records or so in the database. Am I correct in assuming that Access should work ok?
Access should be ok especially if they are mostly doing reads from the database.
Access supports around 10-15 users who are doing updates to tables. If you get
much more than this, a different database should be used.
Your table is quite small, and you have few simultaneous users, so I don't see
why it should be that slow.
Can you elaborate as to what is slow?
Perhaps you have a lot of graphics on the page? If you remove the graphics,
how fast is it then? Are the searches slow? Then you may need to add indexes
on those columns.
Brent
|
|
|
|
Brent
|
| Posted: 04/19/2002, 1:05 PM |
|
To Peter:
>>Access handles 256 simultaneous users (on the web you are only connected during read and
>>write events) and the DB limit is 1 GigaByte for Access2000 and 2 GB for AccessXP (2002).
My old Rambler's speedometer goes up to 120 mph, but I don't believe that either.
I challenge anyone to put 256 users updating an Access database with 1Gb data files.
We can time it to see how quickly it will crash. Like my Rambler, the wheels,
doors, and hood will fall off long before reaching maximum speed. Access will
be in the ditch sooner than you can say "Is the transmission suppose to spark
like that?".
Access is fine for about 12-15 users who are doing updates. More than that and
you are exceeding any and all safety limits. If Access was a car, Ralph Nader
would have recalled it years ago. :)
Brent
|
|
|
|
|
|
