Skip to main content
Databases

MySQL

The database you're already on, and probably haven't looked at in a decade.

MySQL is the database you’re already on. That’s the safest bet anyone could make about a web application built in the last twenty-five years. It came with the hosting, or with WordPress, or with a developer who has used it since university. At no point did anyone sit down and choose it.

Which means nobody has looked at it since either. The useful questions about MySQL aren’t about whether to adopt it. They’re about what your particular installation has been doing for the last ten years without anyone noticing.

“It’s the most popular database in the world”

You’ll be told MySQL is the most widely used database in the world, and there’s nothing to worry about.

Both halves of that are true, but the second deserves more scrutiny than it gets.

Which MySQL are you actually running?

There are two MySQLs, and “we use MySQL” doesn’t tell you which. The Community Edition is GPLv2 and free. The Enterprise Edition is a paid Oracle product with its own tooling for backup, monitoring, auditing and encryption. They share a name and most of a codebase. If nobody in the business can say which one you’re running, resolve that before it appears on an invoice or in a compliance review.

Oracle owns it, and sells a rival

Oracle owns it, and also sells a competing database of its own. There has been no relicensing event, but capability has been moving gradually toward the paid edition, and that direction of travel is the thing to watch.

The silent data problem in older MySQL

This is the one that matters most. Older MySQL will accept bad data without telling you. For much of its history the default configuration would truncate an over-long value or coerce a wrong type rather than reject it. A date nobody validated became a row of zeros. A string too long for its column arrived shortened, with no error raised anywhere. Recent versions reject that behaviour by default, but an installation built before the change and upgraded in place will often have kept its original settings. If your system is old enough, the damage may already be sitting in the tables.

Questions worth asking about your MySQL setup

  • “Are we on Community or Enterprise, and are we paying Oracle for anything?”
  • “What is our SQL mode set to, and has it changed since the system was built?” This is the highest-value one-line technical question on this page, and it takes a developer about thirty seconds to answer.
  • “Which version are we on, and when do the security patches stop?”
  • “If a value had been silently truncated three years ago, how would we find out now?” You’re testing whether anyone has considered it, not commissioning an audit.

When MySQL is still the right database

Most of the time. Ubiquity is an engineering advantage in its own right. Any developer can work on it, every host supports it, every cloud provider offers it managed, and its failure modes are documented by the millions of people who hit them first. WordPress and WooCommerce run on it. For a system whose data is broadly rectangular and whose queries are broadly predictable, MySQL will outlast most of the arguments about it.

Being on MySQL is rarely worth changing on its own account. The cost of moving a working database comes immediately, while the benefit may stay theoretical.

When to modernise or move off MySQL

When the data model is the hard part of the system. If your application’s real difficulty lives in relationships, rich data types or heavy analytical work, PostgreSQL handles that better, and the gap widens as the model gets more complex. Decide it at the start of a build, because it’s expensive to revisit once there’s data in the tables.

When nobody can tell you which edition you’re on or what your SQL mode is. Then the problem is that you don’t currently know what you’re running, and the fix is a conversation rather than a migration.

Alexander De Sousa, Founder of Digital Royalty
Developer’s verdict

Stay on it. Go and find out which one you're running.

I wouldn't move a working system off MySQL to make a point about Oracle. That migration costs you this quarter and the benefit never quite turns up. What I would do this week is find out which edition you're on and what your SQL mode is set to, because both answers are free and one of them occasionally uncovers years of quietly damaged data. If you're starting something new and the data is the interesting part of the problem, that's the moment to look at PostgreSQL instead.

Alexander De Sousa · Founder, Digital Royalty · LinkedIn

Compare it yourself

Compare it against the alternatives

The questions worth asking, answered honestly for MySQL — line it up against any of the alternatives to check the call.

MySQL — at a glance
What it actually is
Relational database
Licence
Dual-licensed: GPLv2 for the Community Edition, or a paid commercial licence for the Enterprise Edition. Which one you are on determines what you may do with it and what it costs.
Has the licence changed?
Not the core licence, but ownership has changed twice — MySQL AB to Sun in 2008, Sun to Oracle in 2010 — and features have progressively moved into the paid Enterprise Edition. The direction of travel is the thing to watch, not a single relicensing event.
Who controls it
Oracle. Development is controlled by a single commercial owner that also sells a competing commercial database, which is the reason MariaDB exists as a fork.
Can you hire for it
Abundant — most developers know it
Paid support available
Yes, from Oracle directly, and independently from Percona and others. Every major cloud provider offers it as a managed service.
Get started

Tell us what you need

A few quick questions, then a straight answer from a real person — usually within a few hours.

What happens next

  1. 1 We reply A real person reads your answers and gets back to you, usually within a few hours.
  2. 2 Questions or a short call If anything isn't clear, we ask by email or book a short call. Before any call we audit your website and make the quick fixes it finds, free.
  3. 3 Your fixed quote A clear, fixed price in writing, within 48 hours of any call. There is no obligation to go ahead.

Tell us what you're working on

Whether it's a new site, a platform, or a process that shouldn't be manual any more — we'll tell you honestly if we can help.