Pick a sample database and write any SELECT against it. Your query runs server-side in a sandbox role with no write privileges.
Avatar rewards
Clear practice challenges and pass all quizzes to unlock rare avatar styles.
Complete your first Beginner course
Complete 2 total courses
Complete 3 total courses
Complete all 6 courses
Pass all course quizzes + complete all practice challenges
Master everything — all courses, quizzes & practice
Practice Path
Pick a level for Clinical Care Performance, then work through challenges one at a time.
All doctors
Challenge 1 of 4 in Easy
List all doctors' first name, last name, and specialty — sorted alphabetically by last name.
No results yet
Run a query to see results here
Learning Map
Use these relationship maps to understand how tables connect before writing joins.
People, departments, and roles
employees
id · first_name · last_name · salary · department_id · job_id · hire_date
departments
id · name
jobs
id · title
Join paths
Customers, catalog, and orders
customers
id · first_name · last_name · email
orders
id · customer_id · order_date
order_items
id · order_id · product_id · quantity · unit_price
products
id · name · category_id · price · stock
categories
id · name
Join paths
Care teams, patients, appointments
patients
id · first_name · last_name
doctors
id · first_name · last_name · specialty · department_id
departments
id · name
appointments
id · patient_id · doctor_id · appointment_date · status · reason
Join paths
Quick tips
Run a small `SELECT * ... LIMIT 10` first so you verify columns and data shape.
Add one table at a time and confirm row counts before adding the next join.
Use clear aliases like `AS total_revenue` so your results are easy to reason about.
Break complex logic into steps with `WITH` blocks to debug each part quickly.
Compare `COUNT(*)` before/after filters and joins to catch accidental row multiplication.
Use explicit `ORDER BY` for deterministic grading and predictable result review.
Built from learner feedback
Thea
“I wanted clear tasks I could complete in sequence, then repeat with confidence. Joins were still the hardest part.”
Sarita
“I needed logical reasoning and plain-language explanations for each command so I could remember it long term.”
Every lesson and challenge has explicit goals, expected output shape, and practical context.
We teach the logic behind SQL clauses, not just syntax, so learners can apply patterns in real work.
Learners can re-run exercises, guided hints, and challenge levels to reinforce skills quickly.