Who answers when a MySQL database fails in production, and how fast?
A named AceMQ senior engineer answers 24/7, with response targets from 15 minutes, by plan, when a MySQL server is down, replication is broken or a disk is full, on self-managed MySQL, Percona Server, RDS or Aurora. Lower severities get a first response within 1 hour, 4 hours or the next business day, and the engineer stays engaged until the root cause is documented.
Which MySQL versions are still supported, and what happens after end of life?
MySQL 8.0 moved to Oracle Sustaining Support on 21 April 2026, and 5.7 did so in October 2023. MySQL 8.4 LTS is the supported line most estates are moving to. AceMQ supports 5.7, 8.0, 8.4 and the innovation releases 24/7, and patched builds through OSSeva keep MySQL 5.7 and 8.0 Community patched while the upgrade is planned.
What breaks when upgrading MySQL from 5.7 or 8.0 to 8.4?
Authentication and defaults. mysql_native_password is disabled by default in 8.4, so clients and accounts still using it fail to connect. From 5.7, the utf8mb4_0900_ai_ci default collation, the removed query cache and stricter SQL modes also bite. We find those accounts and queries first, rehearse the upgrade on a replica and cut over with a tested rollback.
Can you run schema changes on large tables without downtime?
Yes. We use gh-ost or pt-online-schema-change, chosen for your replication topology and table size, with a dry run, a throttle tied to your replica lag budget and a rollback plan. A plain ALTER TABLE on a table with hundreds of millions of rows can queue behind one long SELECT and block every query on the table.
Our replica lags for hours every night. Can that be fixed without new hardware?
Usually. Nightly lag is typically a concurrency problem in the apply path, not a throughput problem on the replica. We check transaction size first, because one large multi-row transaction serialises apply, then the parallel replication settings and whether row-based logging on wide tables inflates the binary log. Splitting the batch into bounded chunks fixes more than extra CPU.
Aurora MySQL, RDS or self-managed: how do you decide?
It depends on your team's operational capacity, read-scaling needs and cost at your data volume. Aurora replaces InnoDB's storage and redo handling with a shared storage layer, so failover time, replica lag and buffer pool tuning all work differently from RDS or self-managed MySQL. We compare them against your workload and state the trade-offs plainly.
What is involved in a MySQL health check?
A MySQL health check reviews index usage and duplicates, replication topology and lag risk, InnoDB configuration against your workload, connection handling, backups and failover readiness. You get a written report with prioritised fixes ranked by production risk. It is a fixed-price engagement, and many teams repeat it quarterly or after major changes.
What does a MySQL consultant from AceMQ do?
Our MySQL consulting covers replication architecture, InnoDB and query tuning, version upgrade planning, online schema change execution, and migration off Oracle or SQL Server. A named senior engineer acts as your MySQL consultant on each engagement, delivers written findings before changing anything, and works alongside your DBAs.
Can AceMQ act as our outsourced MySQL DBA?
Yes, for a defined period and scope. A senior engineer works beside your team on the jobs that need a DBA: slow-query and lock analysis, replication and failover review, schema change planning and upgrade rehearsal. The scope is written before work starts, access is agreed phase by phase, and you keep the runbooks. Ongoing operation, with system access on your infrastructure or ours, is the managed MySQL service.
How is MySQL consulting different from support, a health check or managed MySQL?
Consulting is a defined piece of work with a written result, such as a tuning engagement, a topology review, an upgrade plan or a migration. A health check is the fixed-scope review that often comes first. Support answers incidents 24/7 with response targets from 15 minutes, by plan, for Sev 1. Managed MySQL means AceMQ operates the database day to day. Many teams start with consulting or a health check and move to support or managed afterwards.
Who offers MySQL consulting and professional services?
AceMQ does. Its MySQL consultants are senior engineers who also run MySQL for customers 24/7, and they deliver health checks, version upgrades, migrations and performance tuning as fixed-scope engagements with written results. Oracle's own services and general database consultancies are the other main options; ask any of them who will actually do the work.
How do I choose a MySQL consultant?
Ask who does the work, whether they can show production MySQL experience at your scale (replication, large-table schema changes, 5.7 to 8.0 upgrades), and what you receive at the end. A good MySQL consultant leaves a ranked written plan and runbooks, not only advice on a call.
Can we work with AceMQ on MySQL without a long contract?
Yes. AceMQ works on MySQL in two ways: ad hoc engagements for a defined piece of work, such as a health check, an upgrade or an incident, or an annual partner engagement that covers 24/7 support, proactive reviews and named engineers. Many teams start ad hoc and move to an annual partnership once the first engagement is done.
How much does AceMQ MySQL support or consulting cost?
Every AceMQ proposal is tailored to your requirements: your MySQL environment, the SLA you need, the hours of cover and the scope of work. Most contracts run $24,000–72,000 a year, depending on the SLA, the scope and how MySQL is deployed, with aggressive discounts when several technologies share one contract. Request a quote and AceMQ replies within 1 hour.