|
 |
asp_databases thread: How scalable and reliable is access????
Message #1 by "Kalwinder" <kdohil@t...> on Sat, 19 Jan 2002 16:25:57
|
|
Hi,
I am designing a database to hold approximately 3MB of data. What I am
intending to do is use this database as a backend ayatem to hold the
information that will be displayed on the web. None of this information
will be editable, just readonly. What I want to know is whether Access
will stand the load if thousands of people are accessing the data to be
viewed on the web. I know that access cannot handle more than 5 concurrent
users, but that is if they are updating the information at the same time.
This dadabase's content will only be viewed.
I would also like to know what will be the effects on the database is
thousands of people are viewing the information held in it.
Your help will be most appreciated.
Thanks
Message #2 by Greg Griffiths <greg.griffiths@g...> on Sat, 19 Jan 2002 19:26:02 +0000
|
|
Simple answer is NO. Access is designed for at most a few users on a local
intranet, if you are going to do something like this then consider SQL
Server, Oracle or MySQL.
At 16:25 19/01/02 +0000, you wrote:
>Hi,
>
>I am designing a database to hold approximately 3MB of data. What I am
>intending to do is use this database as a backend ayatem to hold the
>information that will be displayed on the web. None of this information
>will be editable, just readonly. What I want to know is whether Access
>will stand the load if thousands of people are accessing the data to be
>viewed on the web. I know that access cannot handle more than 5 concurrent
>users, but that is if they are updating the information at the same time.
>This dadabase's content will only be viewed.
>
>I would also like to know what will be the effects on the database is
>thousands of people are viewing the information held in it.
>
>Your help will be most appreciated.
>
>
>Thanks
|
|
 |