Find Each Customer's Largest Order in Every Month
Return the highest-value order for each user in each calendar month.
The challenge runs on the SQLabHub practice database (SQLite) and uses the orders table. You can solve it in the browser, with nothing to install.
The task
Find highest value order for each user in each month.
A correct answer returns 198 rows with 11 columns: id, user_id, total, discount, item_count, status, order_date, shipped_date, shipping_city, shipping_country, rn.
Tables used in this challenge
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 | user_id | total | discount | item_count | status | order_date | shipped_date | shipping_city | shipping_country | rn |
|---|---|---|---|---|---|---|---|---|---|---|
First 5 of 198 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
- Filtering rows with a WHERE condition
- Querying the result of another query with a subquery in FROM
- Working with dates in SQLite: strftime, julianday and DATE
- Numbering rows with ROW_NUMBER() to pick one or a few per group
- Restarting a window calculation for each group with PARTITION BY
Hint and approach
Try the challenge first. Open these only when you need them.
Show the hint
ROW_NUMBER partition by user and month
Show the step-by-step approach
How the model solution is built, in the order the database evaluates it:
- Build an inner query first (a derived table):
- Read from the
orderstable. - Number the rows with
ROW_NUMBER(), ordered bytotaldescending, restarting for eachuser_idand the year-month oforder_date.
- Read from the
- Filter in
WHERE: keep the rows wherernequals 1. The filter sits in the outer query because a window function cannot be tested in the WHERE clause of the query that computes it.
Model solution
Checking your session…
What to watch for
PARTITION BY accepts expressions as well as columns: here it combines user_id with the year-month built by strftime, so the numbering restarts for every customer and month pair.
- ROW_NUMBER(). ROW_NUMBER() breaks ties arbitrarily. When the ORDER BY inside OVER does not identify one row, the row that gets number 1 can change between runs.
- PARTITION BY. PARTITION BY is not GROUP BY: it keeps every row and only decides which rows a window function looks at.
- Derived table. Columns computed in the inner query are only visible outside under their alias, so every calculated column there needs a name.
Related SQL challenges
- Find Each Customer's Largest OrderSimilar levelHard
- Find Each Customer's First OrderSimilar levelHard
- Find Orders That Took More Than 3 Days to ShipEasierMedium
- Find Each Customer's Most Recent OrderSimilar levelHard
- Find the Top 3 Most Expensive Products in Each CategorySimilar levelHard
Same technique, other tables
More practice on this pattern with different columns:
Keep learning
- Lesson: ROW_NUMBER()
- Lesson: Window Functions
- Lesson: SQL Subqueries
- Lesson: Date Functions
- All SQL practice challenges, by difficulty and topic
- SQL interview questions with answers
- SQL Playground: run any query on the same database