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.
Instance right-sizing, index pruning, and data lifecycle design — a savings playbook measured against latency, not hope.
Database bills grow for measurable reasons: instances sized for last year's worst moment, indexes nobody queries, and tables that accumulate history forever. Every one of those is reversible — and every reduction can be validated with latency measurements before it lands.
Every index is a write-time tax and a buffer-pool squatter. MySQL's sys.schema_unused_indexes and PostgreSQL's pg_stat_user_indexes make the waste visible. Drop candidates after a full business cycle of observation — then watch write latency improve along with the bill.
Downsizing decisions from peak marketing numbers produce outages. Downsize from p95 utilization over a representative window, with headroom for growth. The instance two sizes smaller than the fear-driven one often costs 40% less and performs identically.
Beyond the job title: the concrete weekly work of backup verification, upgrade planning, and incident response — without a full-time hire.
Bloat, stale statistics, and mystery slowdowns usually trace back to autovacuum settings written for someone else's workload.
Keep your flexible JSON schema and get index-speed lookups: generated columns turn hot JSON paths into first-class index targets.
Work with Burj
Tell us what is slow — CPU, queries, migrations, or cost — and we will scope the smallest safe fix.