|
|||||||||
|
|||||||||
|
|||||||||
 |
|||||||||
| |
||
|
|
|
|
|||||||||
|
|||||||||
|
|||||||||
|
|||||||||
| |
||
|
|
|
| ||||||||||||||||||||||||||||||||
 |
|
|
«
Previous Thread
|
Next Thread
»
|
Thread Tools | Search this Thread | Rate Thread | Display Modes |
ASP Free Forums Sponsor:
|
|
|
|
#1
September 24th, 2003, 10:19 PM
|
|||
|
|||
How big is too big?
I running an access database and using the JET driver but I've been told its slow and sucks for larger databases or databases that get a lot of traffic. But my question is when is too big and when should I update to a better database.
My page doesn't get more than maybe 10 people connected simultaniously. Should I upgrade after 1,000 maybe 10,000 records? Any help would be great. Thanks -Roswell-
|
|
#2
September 24th, 2003, 11:45 PM
|
|||
|
|||
|
For the most part, it's the number of simultaneous connections that is the limiting factor not the db size, and the problem is not really Access but rather the single-threaded Access ADO drivers that eat too many server resources.
10+ simultaneous users is a good rule-of-thumb point to start considering an alternative.
|
|
| Viewing: ASP Free Forums > Database > Microsoft Access Help > How big is too big? |
| Thread Tools | Search this Thread |
| Display Modes | Rate This Thread |
|
|
|
|
|
|
 |
|
|
Del.icio.us
Digg
Google
Spurl
Blink
Furl
Simpy
Y! MyWeb
Linear Mode
