The drawbacks of access as a Web site database

access| Data | database

The vast majority of Web sites are now access+asp form, because access is simple and easy to handle, and can also meet the requirements of most web site procedures.
Access is a small database, and since it is small there is a fundamental limitation, in the following cases the database is basically unbearable:
1. Database is too large, the general Access database up to 50M of time performance will drop dramatically!
2. Site visits are frequent, often reaching 100 people online.
3. The number of records is too high, the general record number reached about 100,000 when the performance will drop dramatically!
(Note: The above 3 is only our experience over the years, and not only the absolute value, depending on the situation of different floating large)

Access Forum (such as dynamic network) after large, it is easy to have problems with the database, when your forum database in more than 30M, post 50,000 or so, online also around 100 people, your forum is basically in the processing database to spend time, this time is likely to be a database unbearable situation.
The general symptom is all the pages involved in the database, the sudden run is surprisingly slow (execution time reached 5 seconds or even a few 10 seconds), the pages involving HTML and pure ASP operations are normal, and so after a period of time (about 10 minutes or longer) after a sudden recovery. This time you can use the general ASP probe test, if the server's operation time is normal, and your word volume is relatively large, is the database aspect of the problem.
Workaround:
Because this is the limitations of access itself, the solution is not only to reduce the amount of data and replace the large database forum is not a good way, which is now often said the forum crisis, but also a large forum is not the reason for access. We recommend the following methods:
1. Temporary solution: Periodically delete redundant data, compress database, limit forum irrigation, and even restrict forum registration. If it is a dynamic network forum, you can use the forum with its own table storage function, will have better results
2. A more long-term approach: the replacement of forums and databases, generally using the dynamic network SQL commercial version of the +mssql solution, but this requires a relatively large investment. Because mssql2000 and access need more resources than they do on memory, they can reach more than 1M per online, and if your SQL forum has 100 people online, it will consume at least 150M of memory from the server.