We’ve supported MySQL since 1999, and current versions through to MySQL 8.4 and 9.
It isn’t our headline specialism — that’s SQL Server and Microsoft Access. But MySQL turns up constantly in the work we do, and when it does we’re comfortable with it. ☎
Where we usually find it
Behind a website. WordPress, WooCommerce, Magento and most web applications run on MySQL. When the site and the office system need to share data — orders, stock, prices, customers — that’s a MySQL job as much as anything else.
Inside an inherited system. Somebody built the business a web application years ago. It works, MySQL is underneath it, and the developer has gone. → legacy software rescue
As one half of an integration. MySQL on one side, SQL Server or Access on the other, and data that needs to move reliably between them.
On a hosting account nobody’s looked at. Running an old version, unpatched, backed up by whatever the host does by default — which is usually less than people assume.
What we do with it
Support and troubleshooting — errors, crashes, connection problems, tables that have stopped behaving.
Integration — joining MySQL to your accounts package, your office system, email, barcode systems and anything else. This is the most common reason people find us for MySQL work → integration and APIs
Performance — slow queries, indexing, configuration and the things that make a website crawl under load.
Recovery — corruption, crashed tables and failed restores → database recovery and data rescue
Migration — version upgrades, moving hosts, and moving to or from SQL Server.
Backups that actually restore — the single most common thing we find wrong on a MySQL system, usually because the host’s default was assumed to be enough → database health check
Data cleansing on MySQL data → data cleansing
MySQL or SQL Server?
Worth answering plainly, since it’s the question people arrive with.
MySQL makes sense where the system is web-based or web-connected, where hosting cost matters, where it’s already there and working, or where whatever you’re running expects it.
SQL Server makes sense where you need serious reporting, where the business is already a Microsoft organisation, where you want integration with Access and Microsoft 365 to be straightforward, or where the workload has outgrown what MySQL is doing for you.
Both are perfectly good databases. The right one is usually whichever one your system already uses — moving between them is a project, and it needs a better reason than preference.
If you do need to move, we do that in both directions → database migration
MySQL causing problems?
Tell us what it's running, what's wrong with it, and what else it needs to talk to. We'll tell you whether we can help — including when the honest answer is that you need a web developer rather than us.
Send us the details →
Call 0114 249 1036 →
MySQL causing problems?
Tell us what it's running, what's wrong with it, and what else it needs to talk to. We'll tell you whether we can help — including when the honest answer is that you need a web developer rather than us.
Send us the details → Call 0114 249 1036 →