Count Orders and Total Spend for Every User, Including Zero
Return every user with their number of orders and total spend, including users with none.
The challenge runs on the SQLabHub practice database (SQLite) and uses the users and orders tables. You can solve it in the browser, with nothing to install.
The task
Find total orders and total spend per user.
A correct answer returns 150 rows with 3 columns: id, total_orders, total_spend.
Tables used in this challenge
users 150 rows
id INTEGER (PK) · first_name TEXT · last_name TEXT · email TEXT · phone TEXT · city TEXT · country TEXT · created_at TEXT · status TEXT · is_premium INTEGER
| id | first_name | last_name | phone | city | country | created_at | status | is_premium | |
|---|---|---|---|---|---|---|---|---|---|
orders 200 rows
id INTEGER (PK) · user_id INTEGER · total REAL · discount REAL · item_count INTEGER · status TEXT · order_date TEXT · shipped_date TEXT · shipping_city TEXT · shipping_country TEXT
| id | user_id | total | discount | item_count | status | order_date | shipped_date | shipping_city | shipping_country |
|---|---|---|---|---|---|---|---|---|---|
The first rows of each table are shown. See how all the tables relate on the database schema page.
Expected output
| id | total_orders | total_spend |
|---|---|---|
First 5 of 150 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
- Summarising many rows into one value with COUNT, SUM, AVG, MIN or MAX
- Grouping rows with GROUP BY to get one result row per group
- Keeping every row of the left table with LEFT JOIN, matched or not
Hint and approach
Try the challenge first. Open these only when you need them.
Show the hint
JOIN + GROUP BY
Show the step-by-step approach
How the model solution is built, in the order the database evaluates it:
- Read from the
userstable. - LEFT JOIN
ordersonusers.id=orders.user_id. Rows from the left side that have no match are kept, with NULL in the joined columns. - Group the rows by
users.id, so the result has one row for each value. - For each group, compute
COUNT(orders.id)andSUM(orders.total).
Model solution
Checking your session…
What to watch for
All 150 users come back. Those with no orders show a count of 0, because COUNT(o.id) skips the NULLs the LEFT JOIN produces, and a NULL total, because SUM of nothing is NULL. Wrap it in COALESCE to show 0.
- LEFT JOIN. A WHERE condition on the right-hand table removes the unmatched rows and turns the LEFT JOIN back into an inner join. Conditions on that table go in the ON clause.
- GROUP BY. Every selected column must either be in GROUP BY or sit inside an aggregate. SQLite accepts other columns and returns an arbitrary value for them; most databases raise an error.
- Aggregate functions. Aggregates skip NULLs. AVG divides by the number of non-NULL values and COUNT(column) can be smaller than COUNT(*).
Related SQL challenges
- Find the Top 15 Customers by Lifetime RevenueSimilar levelMedium
- Count Orders per Month with strftimeSimilar levelMedium
- Total Sales per Order Status with SUM and GROUP BYEasierEasy
- Calculate Each Customer's Order Range (Max Minus Min)HarderHard
- Count Orders by Status with GROUP BYEasierEasy
Keep learning
- Lesson: LEFT JOIN
- Lesson: GROUP BY
- Lesson: Aggregate Functions
- All SQL practice challenges, by difficulty and topic
- SQL interview questions with answers
- SQL Playground: run any query on the same database