Query, Meet Consequence
Write SQL, then see why 'fast enough' was a full scan.
the flame graph reveals that a query returning results in 40ms can still be a full table scan waiting to fall over at 10x the data — the gap between fast today and fast because it's correct, made visible
What goes in, what comes out
The learner writes real SQL against a seeded dataset in a governed sandbox and sees results instantly, same as any query tool. A one-click EXPLAIN flame graph then turns the query planner's internal cost estimate into a visual timeline instead of a wall of text.
write and run SQL against a real seeded database
query results plus an EXPLAIN flame graph showing rows scanned, index usage, and estimated cost
dataset size (10K/1M/10M rows), index-presence toggle, query difficulty tier
Data L1 'Data Before Models'; free lightning lesson; DSAT placement probe
Go deeper, elsewhere
Hand-picked public explainers and open tools that complement this one — always optional, never required, never graded.
Concepts click when you open the machinery.
Three labs are already live and free — the same hands-on style this playground brings to its module.