ALTER classification
Every change mapped to its INSTANT/INPLACE/COPY cost before anyone runs it.
Zero-downtime schema
INSTANT, INPLACE, and COPY — we pick the right ALTER strategy for table size and traffic, or route it through gh-ost/pt-osc when MySQL needs a chaperone.
Diagnosis context
A multi-million-row ALTER on a busy table is a production incident waiting for a scheduling mistake. The work is choosing the cheapest safe path: instant column changes where MySQL 8 allows them, in-place operations where they fit, and online schema-change tooling with throttling where they do not. We plan the path, rehearse it, and execute it inside your traffic envelope.
What the fix plan covers
Every change mapped to its INSTANT/INPLACE/COPY cost before anyone runs it.
gh-ost or pt-online-schema-change runs with throttling tied to replica lag and load.
Constraint ordering and rebuild sequencing that avoids the classic lock-up traps.
The full ALTER executed against a production-size replica first, with timing data.
Execution path
Inventory the changes and classify their execution cost
Rehearse on a production-size replica
Choose the execution window and throttling rules
Execute with live monitoring and a prepared abort path
Verify data integrity and lock behavior after the run
Measured outcome
Schema changes that ship on your schedule — with downtime measured in seconds or zero.
Common Questions
Emergency engagements start with a live diagnostic session — processlist sampling, digest analysis, and parameter review. Stabilization typically lands within one engagement day, with the root cause documented and a monitoring hook to catch recurrence.
Yes, when the strategy matches the change. Instant DDL covers many column operations in MySQL 8; in-place operations fit others; and gh-ost or pt-online-schema-change handle the rest with throttling tied to replica lag. We classify every change before anyone runs it, then rehearse on a production-size replica.
It is an ordering problem, and the fix usually spans both sides. We map the lock graph and specify the transaction re-sequencing your team applies — typically a small, single-commit change. Isolation levels and index design, which are database-side, do most of the heavy lifting.
Because queries filtering or sorting on JSON paths scan without an index. The fix keeps your flexible schema: virtual generated columns over the hot paths, indexes on those columns, and predicate rewrites at the database layer. Your application continues reading the same JSON.
Work with Burj
Tell us what is slow — CPU, queries, migrations, or cost — and we will scope the smallest safe fix.