What a Fractional DBA Actually Does for Your Team
Beyond the job title: the concrete weekly work of backup verification, upgrade planning, and incident response — without a full-time hire.
Keep your flexible JSON schema and get index-speed lookups: generated columns turn hot JSON paths into first-class index targets.
JSON columns are wonderful until a WHERE clause meets them. Without an index, every filter on a JSON path is a full scan. The MySQL 8 answer does not require sacrificing the flexible schema: virtual generated columns plus indexes on those columns give the optimizer a real target.
Mine the digest tables and application queries for JSON_EXTRACT and -> operator usage. Each distinct hot path is a candidate for a generated column. Indexing paths nobody queries is wasted write amplification — measure first.
A generated column typed as the value it extracts (unsigned int, date, char) lets the optimizer use range scans and join statistics. Untyped JSON comparisons force per-row casts. The typing decision is where most of the speed lives.
Beyond the job title: the concrete weekly work of backup verification, upgrade planning, and incident response — without a full-time hire.
Instance right-sizing, index pruning, and data lifecycle design — a savings playbook measured against latency, not hope.
Bloat, stale statistics, and mystery slowdowns usually trace back to autovacuum settings written for someone else's workload.
Work with Burj
Tell us what is slow — CPU, queries, migrations, or cost — and we will scope the smallest safe fix.