Free audit · one database instance · mutual NDA before read-only access · no obligation
View Audit ScopeInnoDB optimization, MySQL 8.0 and 8.4 upgrades, and high availability. Scope the work with a MySQL database consultant.
Selected clients
“They understood our requirements clearly, supported us with the right solutions, and helped us optimize our database in a very short time.”
When to bring in a MySQL consultant
A MySQL database consultant, also called a MySQL DBA consultant, steps in when one of these is costing you sleep. For daily operations, see our MySQL remote DBA service.
Queries got slower as traffic grew, and adding bigger instances stopped helping.
Replicas fall behind during batch jobs, and reads return stale rows.
You are still on MySQL 8.0 and the RDS Extended Support bill keeps growing.
Nobody has timed a full restore, so recovery time is a guess.
Failover has never been tested end to end in production conditions.
The RDS or Aurora bill keeps rising while the workload has stayed flat.
Three ways to work together
An engagement can include an architecture review, InnoDB and query tuning, high availability, ProxySQL routing, and a review of accounts and grants. Start with a free audit, a scoped project, or ongoing DBA support. The same team delivers all three, under one NDA.
A scoped project for one problem or change, with written findings and hands-on implementation.
Engagements scoped before work starts
A read-only review of one MySQL instance, with a prioritized report within one week after access is ready.
What we check on one instance
Monitoring and maintenance in business hours. 24x7 on-call, with a 30-minute P1 target, is available under your support agreement.
What an engagement covers
Every engagement names an owner, and your team sees the evidence before a change is proposed. Percona Server for MySQL consulting follows the same process, with Percona Toolkit and Percona XtraBackup where the platform allows.
innodb_redo_log_capacity from MySQL 8.0.30, innodb_log_file_size before that), and match innodb_io_capacity to measured storage. We also review innodb_flush_log_at_trx_commit, the flush method, and whether the adaptive hash index helps or causes contention. Growth in History List Length and metadata lock waits is traced to the transactions behind it.performance_schema and the sys schema, summarize slow query logs with pt-query-digest, and compare EXPLAIN ANALYZE plans before and after a change. Typical fixes are covering composite indexes, dropping unused or redundant indexes, and rewrites that avoid Using temporary and Using filesort steps.ALGORITHM=INSTANT or INPLACE) where the operation allows it, and gh-ost or pt-online-schema-change for large tables. Upgrades from MySQL 5.7 or 8.0 to 8.4 LTS cover removed variables, reserved words, utf8mb3 to utf8mb4 changes, and the mysql_native_password change, with a rehearsed rollback.performance_schema.metadata_locks and sys.schema_table_lock_waits show who holds the lock and who waits.innodb_io_capacity_max.replica_parallel_workers, GTID settings, and replica I/O before proposing a fix.max_replication_lag. We test failover paths and connection storms before they happen in production.util.checkForServerUpgrade()) reports server-side incompatibilities first. Typical findings are deprecated authentication plugins, removed or changed system variables, new reserved words, and utf8mb3 data that needs utf8mb4. Removed replication statements such as CHANGE MASTER TO are found by reviewing your operational scripts, which the checker does not read.Scaling
MySQL scales by sizing InnoDB for the working set, moving reads to replicas, and adding a cluster when failover is the requirement. The current limit is measured before a change is proposed.
How an engagement runs
From the first call to the handover, here is what happens and what you hold at each step.
MySQL consulting engagement
Step through it, or let it play.
A 30-minute call. No database credentials needed.
What you receive
Not a PDF that sits in a drive. Every finding comes with the evidence, the exact change, how to validate it, and how to roll it back.
Finding
Top statement by total latency in sys.statement_analysis; the plan reads every row, then sorts.
-> Sort: o.created_at DESC, limit input to 20 row(s) per chunk
-> Filter: (o.customer_id = 4821)
-> Table scan on o (rows=486514)ALTER TABLE orders ADD INDEX idx_customer_created (customer_id, created_at), ALGORITHM=INPLACE, LOCK=NONE; -- online, no write lock
ALTER TABLE orders DROP INDEX idx_customer_created;
Where your MySQL runs
An engagement may touch the server, the storage engine, routing, backups, and the cloud service the database already runs on. Managed services hide some knobs. The review names which ones still matter on each platform.
On self-managed Linux hosts, the review also covers kernel and storage settings such as vm.swappiness, transparent huge pages, and noatime mounts on XFS or ext4.
For procurement and security
Signed before any diagnostic access. The scoping call needs no credentials.
Scope, deliverables, acceptance criteria, and fees agreed in writing first.
Read-only by default, named individuals, revoked on completion.
Review meetings, documents, and owners of follow-up work, set in the proposal. Meet the JusDB team
JusDB's security practices are aligned with ISO 27001 and SOC 2 Type II, and JusDB is pursuing both certifications (see Terms, section 12). Read the stated status.
Compare your options
Compare a defined consulting project with hiring internally, using a cloud provider, or buying ongoing support.
| Engagement model | When it fits | Typical scope | Confirm before you choose |
|---|---|---|---|
| JusDB MySQL consulting | A defined performance, reliability, upgrade, or architecture problem that needs specialist investigation. | Agreed project scope, written findings, and a prioritized plan. Implementation is included when agreed in the statement of work. | Objectives, deliverables, access, timeline, change approvals, and who owns the next steps. |
| Ongoing DBA service | Recurring MySQL monitoring, maintenance, and incident support. | Operational coverage and support defined by the provider agreement. | Coverage hours, escalation path, response targets, named owners, and exclusions. |
| Cloud-managed database | A managed platform for database infrastructure and routine platform operations. | Platform features and support covered by the selected cloud service and support plan. | Who owns query tuning, schema changes, upgrades, application issues, and incident coordination. |
| In-house MySQL team | Continuous ownership when MySQL work is closely tied to product and platform priorities. | Direct control over work and decisions, within the team's available time and expertise. | Capacity for specialist diagnosis, major changes, on-call coverage, and documentation. |
Coverage and deliverables depend on the agreement and your MySQL environment.
Workloads
The scoping call is the same. The workload changes which evidence matters.
Common questions
A MySQL database consultant, sometimes called a MySQL DBA consultant, investigates a specific performance, replication, availability, upgrade, or migration problem and explains the evidence behind the diagnosis. Before work begins, JusDB agrees the systems in scope, the access needed, deliverables, timeline, and approval points. A project may include diagnosis, written findings, a prioritized plan, and separately approved implementation and validation, depending on the agreed scope.
The free audit is an availability-dependent, read-only review of one database instance. It ends with a prioritized report within one week after agreed access and inputs are ready; production fixes are not included. Consulting is a separately scoped project for a specific problem or change. Ongoing DBA support is a separate retainer for continued operations and agreed response coverage.
Yes. Depending on the environment and agreed access, we can review slow query logs, execution plans, indexes, InnoDB and performance_schema metrics, and replication health. We establish a baseline, explain the likely causes, and propose changes with a way to validate their effect.
Yes, in most environments. For an upgrade from MySQL 5.7 or 8.0 to 8.4 LTS, JusDB upgrades a replica first, rehearses the cutover on a copy, and then switches traffic to the upgraded replica or through Amazon RDS Blue/Green Deployments, so the application sees a brief connection switch rather than an outage window. Every step has a tested rollback, and the change window is agreed with your team.
We can scope cloud-based MySQL consulting on Amazon RDS for MySQL, Amazon Aurora MySQL, Google Cloud SQL for MySQL, and Azure Database for MySQL Flexible Server, as well as consulting on self-managed MySQL and Percona Server for MySQL. Available diagnostics and change methods vary by platform, so the proposal identifies the systems and permissions needed.
A scoping call needs no database credentials. For diagnostic work, we agree a mutual NDA and customer-approved, least-privilege read-only access to the systems and telemetry in scope. Production changes require separate approval, appropriate permissions, and an agreed validation and rollback plan.
We review enquiries within 2–4 business hours, Mon–Fri 09:00–18:00 IST. A project start date and delivery schedule are confirmed after scope and engineer availability are agreed. Emergency coverage and initial-response targets apply only where they are included in a signed support agreement; a new consulting enquiry is not an emergency response service.
Next step
Tell us what is slow, fragile, or due for an upgrade. You get a written scope and the fees before work starts.
NDA before access · read-only by default · written scope first
