N022-E3 Tier 2 · Core SQL · easy hr · Helix Systems

Return the employee name, department name, and salary amount for every salary record on file

Part of Joining Multiple Tables in SQL

The problem

Helix Systems' payroll team needs a report listing each employee's name, the department they belong to, and their salary amount.

Write a query to return the employee name, department name, and salary amount for every salary record on file.

Assumptions:

  • An employee with multiple salary records appears once per salary in the result.

Output:

  • One row per salary record, with columns employee_name, department_name, and amount.
Schema · hr 4 tables
departments
id integer
name text
location text
budget numeric
salaries
id integer
employee_id integer
amount numeric
effective_date date
end_date? date
employees
id integer
name text
email text
department_id integer
manager_id? integer
hire_date date
title text
is_active boolean
job_history
id integer
employee_id integer
title text
department_id integer
start_date date
end_date? date

Run previews · Check grades

Write a query, then run it to see results here.

Worked solution Try it yourself first
Solution query
SELECT
  e.name AS employee_name,
  d.name AS department_name,
  s.amount
FROM
  employees e
  JOIN departments d ON e.department_id = d.id
  JOIN salaries s ON e.id = s.employee_id

The shape

The chain reaches sideways from employees to departments for the dimension, and forward from employees to salaries for the fact. The result row count is driven by salaries, the one-to-many side — an employee with three salary records contributes three rows, each labelled with the same name and department.

Clause by clause

  • SELECT e.name AS employee_name, d.name AS department_name, s.amount pulls one column from each of the three tables. Both employees and departments have a column called name, so the alias prefix on each is what disambiguates them.
  • FROM employees e anchors the chain on employees.
  • JOIN departments d ON e.department_id = d.id attaches the department. Each employee belongs to one department, so this join doesn't multiply rows.
  • JOIN salaries s ON e.id = s.employee_id attaches every salary record for that employee. This is where the row count comes from — Sarah Chen's two salary records produce two rows in the result, each carrying her name and Engineering department, with the amount column distinguishing them.

You practiced a three-table chain where one of the participating tables is a one-to-many fact (salaries). The recurring rule: the result row count is driven by the most-multiplying table in the chain — here, salaries — not by the dimensions.

How you actually get good at SQL

Reading explains SQL. Writing it, over and over with instant feedback, is what makes you fluent.

That's the whole SQLMaxx loop: 600+ real problems, instant AI feedback, mastery you can actually see, and spaced review that won't let you forget.

A stack of SQL practice problem cards, the top card showing an employees table.
615 problems · 66 concepts

Real problems. Not toy examples.

615 hand-built problems spanning all 66 concepts, from basic SELECTs to window functions, built on real schemas and real business questions, the kind you'll actually get asked on the job. Enough reps to make SQL automatic.

A retro computer showing a SQL query marked correct with a green checkmark.
Instant AI feedback

Write a query. Know if it's right in one second.

No copying an answer and hoping it clicked. The AI grader checks your real query against real data, catches exactly what's wrong, and explains the fix in plain English, like a senior analyst reading over your shoulder on every problem.

A circular mastery progress dial filling from blue to green, the SQLMaxx diamond at its center.
Mastery tracking

Stop guessing whether you actually know it.

SQLMaxx tracks every concept and shows you what you've mastered and what's still shaky. Your skills fill in one concept at a time, so 'I think I get joins' becomes something you can prove.

A SQL query editor circled by a blue return arrow with a clock, scheduled to come back for review.
Spaced review

Learn it once. Keep it for good.

Most of what you learn this week fades by next week. So when a concept comes due for review, SQLMaxx hands you a fresh problem to solve from a blank editor, not a flashcard to re-read. A research-backed spaced-repetition algorithm (FSRS) times each return for right before you'd forget, so your SQL is still there months later, when the interview or the job actually needs it.

Practice, feedback, mastery, review. That's the loop that turns reading into real skill.

Start free

No account, no credit card. Start solving in under a minute.