Which database engine?

We have been working with databases for over 30 years and with small business for over 20.

During that time we have had many discussions with business owners and managers about which database engine they should use. Whilst those discussions have mostly been enjoyable, they have been a waste of time. The decision is quite easy to make:

Anyone reading this article is unlikely to be a database engine decision maker in a large business. We can therefore ignore SQLServer and Oracle. That leaves us with MySQL and Microsoft Access.

If you are a small business and want an on-line database, a web host who provides Access or SQLServer is going to be relatively expensive, with no obvious advantages. You can therefore safely decide on MySQL.

If you need a database that lives on one machine, there is no doubt that you need Access.

We are now faced with the decision of if we need multi-user access on a private network. Access and MySQL will both do this job exceptionally well. In addition, if you use the right developer, the cost of each will be the same, as will speed and ease of access.

Access is easy to install on a server but if the job isn't done properly, grief is the only result. The installation of MySQL requires more work which usually can't be undertaken by an amateur. In any case, the front end needs to be engineered by a professional database designer who is fully aware of your requirements.

Of course, the ultimate choice is yours but if you don't want to store up trouble for the future, discuss your requirements with your database developer.

Database development is not expensive. Mistakes are.