Salary Above Dept Max
Find employees whose salary is equal to max in their department.
The challenge runs on the SQLabHub practice database (SQLite) and uses the employees table. You can solve it in the browser, with nothing to install.
The task
Find employees whose salary is equal to max in their department.
A correct answer returns 10 rows with 12 columns: id, first_name, last_name, email, department, department_id, title, salary, hire_date, manager_id, city, status.
Tables used in this challenge
employees 120 rows
id INTEGER (PK) · first_name TEXT · last_name TEXT · email TEXT · department TEXT · department_id INTEGER · title TEXT · salary REAL · hire_date TEXT · manager_id INTEGER · city TEXT · status TEXT
| id | first_name | last_name | department | department_id | title | salary | hire_date | manager_id | city | status | |
|---|---|---|---|---|---|---|---|---|---|---|---|
The first rows of each table are shown. See how all the tables relate on the database schema page.
Expected output
| id | first_name | last_name | department | department_id | title | salary | hire_date | manager_id | city | status | |
|---|---|---|---|---|---|---|---|---|---|---|---|
The complete result: 10 rows. This is the output of the model solution on the practice database. The task does not fix a sort order, so your rows may come back in a different order.
What you practise
- Returning every column of a table with SELECT *
- Filtering rows with a WHERE condition
- Summarising many rows into one value with COUNT, SUM, AVG, MIN or MAX
- Writing a subquery that refers to the current row of the outer query
Hint and approach
Try the challenge first. Open these only when you need them.
Show the hint
Subquery MAX
Show the step-by-step approach
How the model solution is built, in the order the database evaluates it:
- Read from the
employeestable. - Filter in
WHERE: keep the rows wheresalaryequals the value returned by a subquery. - The subquery is correlated: it refers to the current outer row, so it is evaluated for each row. It works like this:
- Read from the
employeestable. - Filter in
WHERE: keep the rows wheredepartmentequals the outer row'sdepartment. - Aggregate over all the rows that are left: compute
MAX(salary). With no GROUP BY, the result is a single row.
- Read from the
- Return every column with
SELECT *.
Model solution
Checking your session…
What to watch for
- Correlated subquery. A correlated subquery is evaluated per outer row, which gets slow on large tables. A join to a grouped subquery or a window function usually does the same work in one pass.
- Aggregate functions. Aggregates skip NULLs. AVG divides by the number of non-NULL values and COUNT(column) can be smaller than COUNT(*).
- WHERE. WHERE is evaluated before the SELECT list, so it cannot use a column alias defined there or the result of an aggregate.
Related SQL challenges
- Find Employees Earning More Than Their Department AverageSimilar levelMedium
- Find the Highest-Paid Employee in Each DepartmentSimilar levelMedium
- Find Employees Earning More Than 50,000EasierEasy
- Find Employees Earning Above the Median SalaryHarderHard
- Find Employees Earning Above the Company AverageSimilar levelMedium
Keep learning
- Lesson: Correlated Subqueries
- Lesson: Aggregate Functions
- Lesson: WHERE Clause
- Lesson: The BIG 6 SQL Clauses
- All SQL practice challenges, by difficulty and topic
- SQL interview questions with answers
- SQL Playground: run any query on the same database