The app can't open a connection
Every PHP worker and cron job grabs its own connection and holds it, until max_connections is reached and everything else is refused.
Pooled, with sensible limits
Running on MySQL?
MySQL usually keeps running long after it should have been tuned. The site stays up, the slow queries pile up in a log nobody reads, and then one afternoon the pool fills and nothing new can get in. We trace what the server is actually doing and make it stop.
What it is
MySQL is an open-source relational database, first released in 1995 by a small Swedish company called MySQL AB. Sun Microsystems bought the company in 2008, and Oracle picked it up with Sun the year after, which is why the project is now stewarded from Redwood Shores rather than Uppsala.
It is the database sitting under WordPress, Drupal, Magento and a very long list of PHP applications. Rows live inside pluggable storage engines, and almost every site today uses InnoDB, with the old MyISAM engine still lurking in older tables that never got converted. MySQL ships under a dual licence: the GPL version is free to use, and a paid commercial edition exists for shops that cannot accept the GPL terms.
The honest version
No technology is all upside. This is where MySQL earns its place and where it tends to cause trouble.
Sound familiar?
The MySQL problems that bring people to us, and what you have once each one is fixed.
Every PHP worker and cron job grabs its own connection and holds it, until max_connections is reached and everything else is refused.
Pooled, with sensible limits
A missing index, a growing table, or a WHERE clause that the optimiser can no longer satisfy without scanning the lot.
Rewritten, indexed and measured
Extended support ran out in October 2023 and nobody has been brave enough to move to 8.0 because of character set and auth plugin changes.
Upgraded to 8.0 on a rehearsed plan
Usually an old MyISAM table after a power loss or disk issue, sometimes an InnoDB file with buffer pool corruption after a bad shutdown.
Repaired, with the cause removed
Timeouts, max_allowed_packet set too small, or the server killed under memory pressure mid-query.
Settings matched to the real workload
A nightly mysqldump that fails silently, or sits on the same disk as the database it is meant to protect.
Backups tested on a schedule
What we do
Call us for a single slow query, or hand us the whole server.
How it works
Tell us what's going wrong. We look at it, then tell you plainly what's wrong and what it will cost.
We fix the cause, not the symptom. If something is down, getting it back up comes first.
Backups, monitoring, updates and access, so the same problem can't quietly come back.
You get a plain-language write-up. Or we stay on for hosting, upkeep and new work.
Often found together
We work on the whole stack, so the problem can be wherever it actually is.
Your application is opening more connections than max_connections allows and holding them open. Raising the limit buys an hour or two before it happens again. The real answer is almost always a connection pool in front of MySQL and application code that releases connections when it is done with them.
Start by capturing it, either from the slow query log or with EXPLAIN. Most slow queries turn out to be missing an index, scanning more rows than they should, or built in a way the optimiser can't use. The fix is usually a targeted index, a rewritten WHERE clause, or occasionally a schema change, not more hardware.
Yes, if it is rehearsed. The 8.0 jump changes default character sets to utf8mb4, switches the authentication plugin, and removes a handful of deprecated features. We run the upgrade against a copy of your data first, retest the application against it, then schedule the real cutover.
Only if there is a reason beyond preference. MariaDB is close to MySQL but no longer a free swap. PostgreSQL has stricter data handling and better handling of complex queries but requires application changes. We will tell you plainly whether a switch is worth the work in your case.
Usually, yes. For MyISAM tables that come up as crashed, REPAIR TABLE or myisamchk often brings them back. For InnoDB corruption we recover from binlogs and backups rather than trusting a half-broken tablespace. Either way, we also find out what caused it so it does not keep happening.
Estimates are free. Describe the symptom and the environment, and you get a price before any work begins.
Free estimate
Tell us what you're running and what's going wrong. A person reads it and comes back with an estimate.
Your message is with a real person, and we'll get back to you soon.
Rather talk now? Call us: