Skip to content

Programme outline

Build Confident SQL Admin Skills Without Guesswork.

This page is the short version of the QueryPilot Academy story — written so that an operator can share it with a manager in a single read. The three sections below sit in the order they tend to be discussed: what the program covers, how the labs are run, and what a participant carries back to their team.

Section 01

Program Overview

The QueryPilot catalogue runs across four tracks — Foundations, Operations, Performance, and Recovery — with corporate engagements available alongside the public cohorts. Each program is a fixed-length cohort: two to eight weeks of mentor-led labs against shared and personal sandboxes, with a written closing artefact at the end. The tone is unflashy by design.

  • Foundations

    SQL Foundations for Operators

    4 weeks · Live cohort

  • Operations

    Day-Two PostgreSQL Operations

    6 weeks · Live cohort

  • Operations

    MySQL Administration in Practice

    4 weeks · Hybrid

  • Operations

    SQL Server Care for Mixed Stacks

    4 weeks · Live cohort

Curriculum schema

Studio Foundations Operations Performance Recovery Tracks share mentors, sandbox, and the closing-review template.

Section 02

Practice Labs

Every cohort runs in a sandbox the studio maintains — disposable replicas, a write-heavy synthetic workload generator, and a small library of inherited-schema scenarios used for diagnostic exercises. Labs are timed but not graded; the deliverable is a written reflection per session, not a score. Mentor reviews focus on the operator’s reasoning rather than the elegance of the SQL.

  • Disposable PostgreSQL, MySQL, MariaDB, and SQL Server replicas refreshed nightly.
  • A synthetic write-heavy workload generator for tuning and recovery rehearsals.
  • Pre-tangled inherited schemas for diagnostic clinics.
  • Paired drill format with peer observation and a written verification note.
  • Mentor-only review channel, not a public leaderboard.

Section 03

Learner Outcomes

We talk about outcomes as habits rather than promises. The closing review is the moment a participant articulates the change in their own voice; what follows is a representative sample of the language that surfaces.

  • 01

    I can read EXPLAIN slowly and explain it to a non-DBA colleague.

  • 02

    I have a verification report template I am willing to publish to my team.

  • 03

    My next on-call rotation will have a runbook that the half-asleep version of me can use.

Schedule an introduction
QueryPilot Academy