MySQL support

MySQL Support for Self-Managed Servers, RDS, Aurora and Percona

Last reviewed by Tyler Eastridge

AceMQ supports MySQL 24/7 across Americas, EMEA and APAC on self-managed servers, Amazon RDS and Aurora, Azure and Google Cloud managed instances, and Percona Server. Most calls begin with one of three problems: replicas that fall behind during batch work, locking that stalls writes, or an 8.0 to 8.4 upgrade that has to be rehearsed before cutover.

AceMQ provides 24/7 MySQL support from named senior engineers, with response targets from 15 minutes, by plan, to a production emergency, for self-managed servers, RDS, Aurora and Percona. MySQL 8.0 has been in Oracle Sustaining Support since April 2026, so we also run the 8.0 to 8.4 LTS upgrade as a project, with the support contract in place while it happens. Replica lag, InnoDB deadlocks, ALTER statements that hold a metadata lock for hours and binlogs filling a volume are the daily work.

Support quotes answered within 1 hour, by a senior engineer.

Planning a build, upgrade or migration instead? See AceMQ MySQL consulting and services.

160+
Customers supported
10+
Years in production support
40+
Sev 1 incidents handled a year
24/7
Americas, EMEA and APAC
1hour
Quote reply

Customers

  • Microsoft
  • Henry Schein
  • Enbridge
  • Gojek

Partners

  • Broadcom
  • Redis
  • VMware Tanzu
  • OSSeva

Incident Triage

Problems we fix every week

Replication lag, slow queries, purge backlog and failover storms, each with the InnoDB status, performance_schema or replica metric we open first.

Common MySQL production problems and how AceMQ resolves them
Symptom you're seeingWhat we check first
Replica lag appears only when a large transaction commitsCheck SHOW REPLICA STATUS for Seconds_Behind_Source next to the applier state in performance_schema.replication_applier_status_by_worker. A single multi-million-row transaction serialises the applier, so the answer is batch size and replica_parallel_workers, not hardware.
Queries get slower after a data load, with no code changeCompare EXPLAIN ANALYZE before and after, then check persistent statistics (innodb_stats_persistent, ANALYZE TABLE). Skewed histograms and stale statistics flip join order.
History list length keeps growingCheck SHOW ENGINE INNODB STATUS for "History list length" and information_schema.innodb_trx for the oldest open transaction. A forgotten session with an open transaction holds back purge for the whole instance.
Group Replication or InnoDB Cluster loses a memberCheck performance_schema.replication_group_members and the member's error log for the certification or flow-control message. We separate network, applier lag and a transaction that cannot be certified.
Connection storms follow a failoverCheck Threads_connected, max_connections, Aborted_connects and the application pool's reconnect behaviour. A pool that retries without backoff turns a ten-second failover into minutes.
Temporary tables spill to disk and the volume fillsCheck Created_tmp_disk_tables, tmp_table_size and the tmpdir volume, then the query shapes behind it: large sorts, GROUP BY on unindexed columns, wide TEXT columns in the select list.
A backup restores slowly or incompletelyTime a real restore, and verify the binary log position or GTID set it recovers to against what point-in-time recovery needs.

A written analysis follows each P1, naming the statement, setting or replica responsible.

Replica lagging behind or a failover gone wrong? Ask for a quote and expect a MySQL engineer's reply within the hour.

Contact Us

Deployment coverage

Which MySQL deployments does AceMQ support, and who covers what?

DeploymentWhat AceMQ coversWhat the vendor or platform coversExcluded
Self-managed Community or Enterprise EditionIncidents, replication, backup and recovery, tuning, upgrades, security configurationOracle covers MySQL Enterprise Edition under its subscriptionDefects needing a patch to Oracle's code
Amazon RDS and Aurora MySQLSchema, indexes, query tuning, parameter groups, replication design, upgrade planningAWS runs the service, engine patching windows and failoverFaults in the AWS service layer
Azure Database for MySQL and Cloud SQLThe same, using each platform's parameter modelThe cloud provider runs the platformProvider control-plane faults
Percona Server and XtraDB ClusterOperations, tuning and upgradesPercona covers its own subscriptionsPercona-only tooling defects
InnoDB Cluster and Group ReplicationTopology, certification and flow-control problems, router behaviourOracle for product defects with a subscriptionApplication-side connection logic

Support options

Oracle MySQL Enterprise support or independent support?

Oracle MySQL Enterprise Edition
AceMQ independent support
Support offerOracle says MySQL Technical Support Services give "24x7 direct access" to MySQL support engineers
Support offer24/7, response targets from 15 minutes, by plan
Bundled withEnterprise Edition features such as Enterprise Backup, Audit and Firewall
Bundled withOperations of the edition you run; Community Edition covered
Who fixes product defectsOracle
Who fixes product defectsWe reproduce and work around; no vendor patches
PricingNot shown on the product page
Pricing$24,000 to $72,000 a year (USD), by SLA, scope and deployment

What's Included

Everything in your MySQL support contract

MySQL services under one contract: incident response, query and index tuning, replication and high availability review, schema changes, and consulting on upgrades and migrations between self-managed and managed MySQL database services.

  • 01

    Emergency Incident Response

    Server down, replication broken, disk full, or a table locked behind a runaway DDL. With response targets from 15 minutes, by plan, a senior engineer joins a live bridge with access to diagnose — not a ticket acknowledgement.

  • 02

    Root Cause Analysis

    Every P1 closes with a written RCA: what failed, why, the fix applied, and the schema, index, or configuration change that stops it happening again. Delivered as standard, not on request.

  • 03

    Query & Index Tuning

    EXPLAIN ANALYZE on your real slow log, composite index ordering, covering indexes, histogram statistics for skewed columns, and killing the temp-table spills that come from unindexed GROUP BY and ORDER BY.

  • 04

    Replication & HA Review

    GTID hygiene, semi-synchronous replication trade-offs, InnoDB Cluster and Group Replication behaviour under partition, and failover automation that fails over for the right reasons.

  • 05

    CVE & Patch Advisory

    Alerts for CVEs affecting your exact MySQL, Percona, or MariaDB build, with tested upgrade paths — including the 5.7 to 8.x jump where authentication plugin and collation changes break clients.

  • 06

    Online Schema Change & Migrations

    Large table alterations with gh-ost or pt-online-schema-change, major version upgrades, and migrations between self-managed, RDS, Aurora, and Percona — planned with a rehearsed rollback.

Why AceMQ

Why MySQL teams call AceMQ

  • Named Engineers, Zero Cold Start

    The same senior engineers stay on your account. They know your schema, your replication topology, and your batch windows — so a P1 call starts with a hypothesis instead of twenty minutes of context transfer.

  • No First-Line Triage Layer

    You reach a senior MySQL engineer directly by phone, email, or Slack. Nobody collects information to hand off, and there is no escalation approval between you and the person who can read an InnoDB status dump.

  • Schema Changes Without the Outage

    Large table DDL is where most MySQL maintenance goes wrong. We plan alterations with gh-ost or pt-online-schema-change, measure the throttle against your replica lag budget, and rehearse the cutover before it touches production.

  • Aurora, RDS, and Self-Managed Are Not the Same

    Aurora MySQL replaces the storage and redo layer outright, which changes failover, replica lag, and what buffer pool tuning even means. We support all three models and know which advice stops applying where.

  • Genuine Follow-the-Sun Coverage

    Round-the-clock coverage for customers in 26+ countries. Your 3am replication break is someone's mid-afternoon — no overnight skeleton crew, no waiting for a region to come online.

  • Full-Stack, Not Just mysqld

    We diagnose across the connection pool, the ORM's generated SQL, storage latency, filesystem and kernel settings, and Kubernetes. MySQL symptoms often have causes well outside the database process.

MySQL platforms we cover

Self-managed servers, Percona builds, RDS, Aurora, Azure and Cloud SQL instances, and InnoDB Cluster topologies.

  • MySQL 5.7 (EOL) through 8.4
  • Amazon RDS for MySQL
  • Amazon Aurora MySQL
  • Azure Database for MySQL Flexible Server
  • Google Cloud SQL for MySQL
  • Percona Server & XtraDB Cluster
  • MariaDB
  • InnoDB Cluster / Group Replication
  • Kubernetes & OpenShift operators
  • Bare metal & on-premise
  • Air-gapped / no outbound access
  • Hybrid cloud

Version coverage

MySQL versions we support

MySQL versions we support
Release lineWhat we do on it
8.4 LTS24/7 support and the recommended upgrade target
Innovation releases24/7 support for teams that track them
8.024/7 support and an 8.0 to 8.4 upgrade project
5.724/7 support and an upgrade project through 8.0

What changes between 8.0 and 8.4 is listed under upgrades: removed replication statements (CHANGE MASTER TO becomes CHANGE REPLICATION SOURCE TO), the disabled mysql_native_password plugin and changed InnoDB defaults.

In practice

What does MySQL performance tuning cover, and what does it cost?

Tuning covers slow-query analysis with EXPLAIN ANALYZE and the slow query log, index review, InnoDB buffer pool and redo log sizing, replication applier settings, connection handling and parameter group review on RDS or Aurora. It sits inside a support contract, or as a scoped health check quoted within 1 hour. AceMQ support runs from $24,000 to $72,000 a year (USD), set by SLA, scope and deployment.

Percona Server

Percona Server support

AceMQ supports Percona Server and Percona XtraDB Cluster 24/7, with response targets from 15 minutes, by plan: operations, tuning and upgrades under the same contract as MySQL Community and Enterprise Edition, Amazon RDS and Aurora. Percona covers its own subscriptions and Percona-only tooling defects, which stay with Percona.

Typical work is replica lag and locking, large table alterations with gh-ost or pt-online-schema-change, CVE alerts for your exact Percona build, and migrations between self-managed, RDS, Aurora and Percona, planned with a rehearsed rollback.

Version paths are on MySQL upgrades.

Escalation Path

Your first hour of a MySQL outage

A primary that stopped accepting writes gets an engineer who has read plenty of InnoDB status output, so diagnosis starts at once.

  1. From 15 min (by plan)first responseEmergencyProduction outage: the primary will not accept writes, replication is broken, or the data volume has filled
  2. 1 hourfirst responseCriticalSerious degradation: replica lag measured in minutes, a Group Replication member lost, connection exhaustion after failover
  3. 4 hoursfirst responseHighGrowing history list length, queries regressing after a load, temporary tables spilling to disk
  4. Next Dayfirst responseStandardIndex and query review, ALTER planning, upgrade steps, backup and restore timing, parameter group advice

Targets depend on plan, so a primary that cannot commit is not treated like an index question.

Prefer a named MySQL engineer who knows your topology? Get a quote or contact us.

Contact Us

Pricing

What does AceMQ MySQL support cost?

MySQL support commonly runs $24,000 to $72,000 a year. The figure reflects the number of servers and replicas, whether you use InnoDB Cluster, Aurora or RDS, and the response level you select.

All prices in US dollars (USD). Response targets start at 15 minutes by plan, 24/7; quotes are returned within 1 hour. Covering several technologies in one contract earns a discount.

Support In Practice

MySQL replication and schema work

MySQL support work from AceMQ. Each card links to the full write-up: the database estate, what AceMQ diagnosed or changed, and the result.

1 / 6 case studies

  • Remediation

    MySQL Replication Lag Remediation

    E-Commerce Marketplace Operator

    Resolving replica lag that grew to hours during batch windows because single-threaded apply could not keep pace with large multi-row transactions.

    MySQLProxySQLPrometheusLinux
  • Support

    MySQL InnoDB Lock Contention Support

    Travel Booking Platform

    Ongoing support for deadlocks and lock wait timeouts under booking concurrency, including history list growth from long-running transactions.

    MySQLProxySQLPrometheusKubernetes
  • Assessment

    CloudStack LTS Upgrade Assessment: Java 17, System VMs and Hypervisor Agents

    Private Cloud Operations Team

    A typical engagement to plan an Apache CloudStack upgrade onto the current LTS line: read every upgrade guide between the running version and the target, check Java 17 on the management servers and KVM agents, and write the order of management servers, hosts and system VMs.

    Apache CloudStackKVMMySQLJava
All use cases

Support options

Four tiers of MySQL support.

AceMQ offers MySQL support in four tiers, each handing more of the day-to-day work to AceMQ: 24/7 support and incident management for servers your DBAs run, proactive monitoring that finds replica lag, errant GTIDs and backup gaps first, managed MySQL on your own infrastructure, and fully managed MySQL on AceMQ infrastructure. MySQL 5.7 to 8.4 is supported, and 5.7 and 8.0 can be kept patched through OSSeva.

  • Tier 1

    MySQL 24/7 Support & Incident Management

    Your DBAs run mysqld, we take the hard calls

    Best for: Teams with in-house DBAs who want a senior MySQL engineer for replication failures and unexplained slowdowns.

  • Tier 2

    MySQL 24/7 Support with Proactive Monitoring

    Regular reviews of queries, replicas and backups

    Best for: Teams that want lag, purge backlog and restore time checked on a schedule before they cause an outage.

  • Tier 3

    Managed MySQL on Your Infrastructure

    We administer MySQL on servers you control

    Best for: Businesses that must keep MySQL in their own data center or cloud account but want daily upkeep handled.

  • Tier 4

    Fully Managed MySQL on AceMQ Infrastructure

    AceMQ operates MySQL for you as a service

    Best for: Teams that need a reliable relational backend without hiring and rostering their own DBAs.

FAQ

MySQL support questions

Still have questions about MySQL? Email an Expert

Who provides enterprise support for MySQL?

Oracle, through MySQL Enterprise Edition, plus Percona and cloud providers for their own products. AceMQ provides independent 24/7 support for the MySQL you run on any of those platforms.

Why is my replica always behind after the nightly batch?

Lag after a batch usually means a big transaction applies serially on the replica. We check the applier settings, parallel replication options and the binlog format, then split or reschedule the batch. Often the cure is the job design, not bigger hardware.

How do I run an ALTER on a very large table safely?

Use an online method (ALGORITHM=INPLACE where the change allows it, or a tool such as gh-ost or pt-online-schema-change), watch metadata locks with performance_schema.metadata_locks and set lock_wait_timeout low so a blocked change gives up instead of blocking the application.

Can you run the 8.0 to 8.4 upgrade without downtime?

Rehearse on a replica first, replay real traffic, then promote. Replication from an older source to a newer replica is supported and the reverse is not, so the rollback is planned before cutover.

Do you support Aurora and RDS MySQL?

Yes: schema, queries, parameter groups and replication design. AWS runs the service.

Does a MySQL Enterprise Edition licence replace independent support?

Not necessarily. Oracle's subscription covers the product; we cover the operations around it, and Community Edition servers that have no vendor.

How do I repair a corrupt MySQL table?

First identify whether it is a storage fault or logical damage, restore from backup where possible, and use innodb_force_recovery only to export data, never to continue running.

How fast do you respond to a MySQL outage?

From 15 minutes on the fastest plans, any hour. A common Sev 1: the primary stops committing and SHOW ENGINE INNODB STATUS shows a long-running transaction holding locks. An engineer joins you, finds the blocker, restores writes and documents the cause. P2 is 1 hour, P3 4 hours, P4 next business day.

Can we engage AceMQ for one MySQL task?

Yes. A major version upgrade, a replication rebuild or a large online schema change can be quoted as its own piece of work. Teams often add an annual agreement afterward, so the engineers who ran the project stay available around the clock for incidents.

How does AceMQ price MySQL support?

Yearly MySQL contracts typically fall between $24,000 and $72,000 (USD). We scope by servers and replicas, cluster style (single primary, InnoDB Cluster or Aurora), how many schema changes and upgrades you expect, and your response plan. Describe the estate in a request and a quote follows within 1 hour.

Let's talk

Your MySQL Estate Shouldn't Depend on One Person's Memory

Send us your topology and version. We reply with a quote within 1 hour and can begin with a baseline health check.

A senior MySQL engineer, not a sales queueQuote requests answered within 1 hourAd hoc engagements or an annual partnership

Production incident right now?Email a MySQL Architect