Highest Monthly Sales Spike
Find products with biggest jump in monthly sales.
The challenge runs on the SQLabHub practice database (SQLite) and uses the orders and order_items tables. You can solve it in the browser, with nothing to install.
The task
Find products with biggest jump in monthly sales.
A correct answer returns 470 rows with 3 columns: product_id, month, spike.
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 |
|---|---|---|---|---|---|---|---|---|---|
order_items 496 rows
id INTEGER (PK) · order_id INTEGER · product_id INTEGER · quantity INTEGER · unit_price REAL · subtotal REAL
| id | order_id | product_id | quantity | unit_price | subtotal |
|---|---|---|---|---|---|
The first rows of each table are shown. See how all the tables relate on the database schema page.
Expected output
| product_id | month | spike |
|---|---|---|
First 5 of 470 rows. This is the output of the model solution on the practice database.
What you practise
- Summarising many rows into one value with COUNT, SUM, AVG, MIN or MAX
- Grouping by more than one column to get a row per combination
- Combining rows from two tables on a matching key with an inner join
- Querying the result of another query with a subquery in FROM
- Working with dates in SQLite: strftime, julianday and DATE
- Reading the previous row's value with LAG()
- Restarting a window calculation for each group with PARTITION BY
- Sorting the result with ORDER BY
- Deriving a new column from an expression and naming it with an alias
Hint and approach
Try the challenge first. Open these only when you need them.
Show the hint
LAG monthly revenue
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
order_itemstable. - Join
ordersonorder_items.order_id=orders.id. - Group the rows by
order_items.product_idandmonth(the year-month oforders.order_date), so the result has one row for each combination. - For each group, compute
SUM(order_items.subtotal).
- Read from the
- Fetch
revenuefrom the previous row withLAG(), ordered bymonth, restarting for eachproduct_id. Where there is no such row the value is NULL. - Combine those values into
spike:revenue - LAG(revenue) OVER (PARTITION BY product_id ORDER BY month). - Sort the result by
spikedescending.
Model solution
Checking your session…
What to watch for
- LAG(). LAG() returns NULL for the first row of each partition, and any arithmetic with that NULL is NULL too. Supply a default as the third argument if you need a number.
- 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
- Calculate Month-over-Month Revenue Change per ProductSimilar levelHard
- Measure Monthly Revenue Volatility per ProductSimilar levelHard
- Calculate Monthly Revenue with strftimeEasierMedium
- Calculate the Average Days Between Orders per CustomerSimilar levelHard
- Find the Longest Run of Consecutive Order Days per CustomerSimilar levelHard
Keep learning
- Lesson: LAG & LEAD
- Lesson: Window Functions
- Lesson: SQL Subqueries
- Lesson: INNER JOIN
- All SQL practice challenges, by difficulty and topic
- SQL interview questions with answers
- SQL Playground: run any query on the same database