HardSQL challenge #280WINDOW FUNCTIONPARTITIONDATE

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.

Solve This SQL Challenge

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

First 3 rows of the orders table
iduser_idtotaldiscountitem_countstatusorder_dateshipped_dateshipping_cityshipping_country
1432638.110.253cancelled2024-04-24NULLLos AngelesUSA
2829470.195delivered2024-03-152023-04-09ChicagoUSA
3136683.240.082delivered2023-02-152023-07-10Los AngelesUSA

The first rows of each table are shown. See how all the tables relate on the database schema page.

Expected output

Expected output of the challenge
iduser_idtotaldiscountitem_countstatusorder_dateshipped_dateshipping_cityshipping_countryrn
10914064.750.043delivered2022-09-262023-09-19AustinUSA1
1321618.290.233delivered2023-04-022024-04-02SeattleUSA1
8742501.2306delivered2022-08-222024-09-16San FranciscoUSA1
1814843.705shipped2024-04-202023-01-18CharlotteUSA1
1141518.360.091processing2024-11-15NULLDenverUSA1

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:

  1. Build an inner query first (a derived table):
    1. Read from the orders table.
    2. Number the rows with ROW_NUMBER(), ordered by total descending, restarting for each user_id and the year-month of order_date.
  2. Filter in WHERE: keep the rows where rn equals 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.
Solve This SQL Challenge

Same technique, other tables

More practice on this pattern with different columns:

Keep learning