Have Geek Brain

Should you redesign your ecommerce site to use mySQL instead of Access?

I am doing some work on an asp site that uses Access as its database.

The site has been experiencing unexplained downtime lately, and we are wondering if building a completely new site and switching to PHP from mySQL will bring big performance gains or not.

This is a pretty busy site with a maximum of 80 installed at the same time.

+1


a source to share


8 answers


It is impossible to definitively answer the question "is it worth it"?

However, for your situation, I would say that the first thing you need to do is turn "unexplained downtime" into "explained downtime". Find out what is causing the problem. If it turns out to be a hardware error on the server, you are about to rewrite the entire site and it will continue to decline anyway.



Then, if you determine that it is a db issue causing the problem, the next thing I will do is just go to MySQL, but leave the site in ASP. If you are just concerned about the database, why are you also considering rewriting PHP?

+11


a source


Access is for small workgroups. It only supports 2GB of data per database and is not really designed for 80 concurrent users. I highly recommend switching the more reliable RDBMS.



+3


a source


Hell yes! It scares me that such a site works on it.

+2


a source


MySQL provides much better performance than Access. MySQL is capable of handling much more concurrent connections than Access.

I'm surprised to see Access handling 80 connections - I've usually seen it crash after the first dozen or so.

+2


a source


Another thing to worry about about Access is that since it was not designed to efficiently manage multiple users at the same time, data corruption could lead to an ugly head. MySQL or SQL Server can handle a ton of users much better. However, I agree with Chad Birch that you should leave the site in ASP to avoid the headache when switching to PHP.

+2


a source


I would say yes. I don't think access was really meant to manage data centric websites, nor is it as strong as a database engine like MySQL or SQL Server.

+1


a source


I would walk away from Microsoft Access entirely. Over time, I learned that exclusive open and intermittent web user locks can cause Access to be unavailable and that there is no good solution to fix this.

Files

.mdb are known for their corrupt experience.

I use Access as a tool to visually build queries, but never for a repository, unless it's very trivial and never used for a web application (never again, ever.)

I don't know PHP will help you. But changing the DB will help you.

+1


a source


SQL Server / Express would be a big improvement or just a SQL.mdf file if your provider doesn't have SQL Server.

0


a source






More articles:


All Articles