Calculate Week-over-Week Revenue Change
Return each week with the change in revenue compared with the previous week.
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
Calculate weekly revenue growth.
A correct answer returns 108 rows with 2 columns: week, growth.
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
| week | growth |
|---|---|
First 5 of 108 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
- 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()
- 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
strftime week + LAG
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. - Group the rows by
week(the year-week oforder_date), so the result has one row for each value. - For each group, compute
SUM(total).
- Read from the
- Fetch
revenuefrom the previous row withLAG(), ordered byweek. Where there is no such row the value is NULL. - Combine those values into
growth:revenue - LAG(revenue) OVER (ORDER BY week).
Model solution
Checking your session…
What to watch for
strftime('%Y-%W') labels each date with its year and week number, with weeks starting on Monday. Weeks without orders have no row, so the previous row is the last week that had sales.
- 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.
- Derived table. Columns computed in the inner query are only visible outside under their alias, so every calculated column there needs a name.
- 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.
Related SQL challenges
- Calculate the Day-to-Day Change in RevenueSimilar levelHard
- Calculate Month-over-Month Revenue Change per ProductSimilar levelHard
- Calculate Monthly Revenue with strftimeEasierMedium
- Calculate Day-over-Day Revenue Growth in PercentSimilar levelHard
- Find the Longest Gap Between Orders for Each CustomerSimilar levelHard
Keep learning
- Lesson: LAG & LEAD
- Lesson: SQL Subqueries
- Lesson: GROUP BY
- 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