Find Employees Earning More Than 50,000
Return the employees whose salary is above 50,000.
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 with salary greater than 50000.
A correct answer returns 119 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 | |
|---|---|---|---|---|---|---|---|---|---|---|---|
First 5 of 119 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
Hint and approach
Try the challenge first. Open these only when you need them.
Show the hint
Use WHERE salary > value
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 wheresalaryis greater than 50000. - Return every column with
SELECT *.
Model solution
Checking your session…
What to watch for
Numbers are written without quotes or thousands separators. > leaves out anyone earning exactly 50,000; use >= if the threshold itself should count.
- WHERE. WHERE is evaluated before the SELECT list, so it cannot use a column alias defined there or the result of an aggregate.
- SELECT *. SELECT * is fine for exploring, but its output changes whenever a column is added to the table. Queries that feed a report should name their columns.
Related SQL challenges
- Filter Rows After a Given DateSimilar levelEasy
- Exclude a Value with the Not Equal OperatorSimilar levelEasy
- Find Employees Earning Above the Company AverageHarderMedium
- Filter Rows Where a Column Equals a Text ValueSimilar levelEasy
- Compare Two Columns in a WHERE ClauseSimilar levelEasy
Same technique, other tables
More practice on this pattern with different columns:
Keep learning
- 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