The author used the Access database to create a website, but later found that the amount of data increased and the speed was slow, so everyone must make long-term plans before building a website.
How many records can an Access database have? , what is the maximum file size of Accsee?
Theoretically there is no limit, but it is generally not useful if it exceeds 100,000.
Access does not support large amounts of data very well. The largest mdb file is 1G. It will not work no matter how you add records. There will be no errors and no prompts, but the data cannot be added. The specific number of records depends on the size of the record. I have records with more than a dozen fields, and there are about 500,000 records like this.
I didn't think much about this problem before I started building a website, because the average enterprise website doesn't have much data, and the mdb file usually doesn't exceed 100M, but recently I've been troubled by this problem.
A customer's website has more than 3W records and a size of about 300M. After multiple compressions, it is still more than 280M. The speed is very slow now.
Investigate the reasons, analyze the following two points:
1. Access does not support large amounts of data very well, and it was not fully considered before building the website. Not fully understanding customer needs. For large data volume needs, SQL or MYSQL database should be considered. That is, the ASP+ACCSEE version cannot be used.
2. There were problems with the original design modules and classification. The entire site has only one article module, and everything else is classified under this module, which directly leads to an excessive amount of data in the jtbc_article table. Basically, more than 30,000 records are all in this table. Causes query speed to slow down.
Therefore, when building a website, articles of the same nature but different categories should be built in different modules, that is, cloning multiple article modules, which can not only effectively solve the above problems, but also better pass the module homepage template node index to customize personalized homepages for different categories.
But now I am still entangled with this problem, because it is very troublesome to separate the modules again with so much data, and it is not the most effective solution in the end, because the data is still growing every day, and there will be at least 100,000 pieces of data. So the ACCESS database should be given up.
More importantly, I want to abandon IIS and replace it directly with PHP+MYSQL. This way, when deploying the server, I don’t need to install the annoying IIS. I can just use apache or Nginx, which is several times more efficient than IIS. But the problem now is that the functions in the PHP version are not as strong as ASP. This is not a problem, because this site does not need any powerful functions. The key is that HTML generation can be used, but the PHP version I tested has been unable to generate static. That's what really bothers me.