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.
Why the slowest queries in production are rarely the ones you think, and how to rank work by total latency contribution.
Most teams optimize the queries users complain about. The problem: user-visible slowness and total latency cost are different rankings. The query that made one customer angry yesterday is not necessarily the one eating 60% of your database time every minute.
Total-cost thinking is the foundation of every slow-query optimization engagement we run.
On MySQL, digest tables give you statement templates with aggregated timing; on PostgreSQL, pg_stat_statements does the same. Sort by total time, not mean time. The top of that list is where engineering hours earn their keep.
Plans change with data volume, statistics, and parameters. A plan comparison before and after each change — actual rows, actual time, buffer usage — is the only record that proves an optimization worked. Keep the deltas; they become your performance history.
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.