Top Revenue Orders
Find orders contributing to top 20% revenue.
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 orders contributing to top 20% revenue.
A correct answer returns 40 rows with 11 columns: id, user_id, total, discount, item_count, status, order_date, shipped_date, shipping_city, shipping_country, bucket.
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 | bucket |
|---|---|---|---|---|---|---|---|---|---|---|
First 5 of 40 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
- Splitting rows into equal-sized buckets with NTILE()
Hint and approach
Try the challenge first. Open these only when you need them.
Show the hint
NTILE(5)
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. - Deal the rows into 5 equal-sized buckets with
NTILE(5), ordered bytotaldescending.
- Read from the
- Filter in
WHERE: keep the rows wherebucketequals 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
- NTILE(). NTILE() balances the number of rows per bucket, not the values. Rows with the same value can end up in different buckets.
- Derived table. Columns computed in the inner query are only visible outside under their alias, so every calculated column there needs a name.
- WHERE. WHERE is evaluated before the SELECT list, so it cannot use a column alias defined there or the result of an aggregate.
Related SQL challenges
- Find the Top 10% Most Expensive Products with NTILESimilar levelHard
- Split Employees into Salary Quartiles with NTILE(4)Similar levelHard
- Find Each Customer's Largest OrderSimilar levelHard
- Find Each Customer's First OrderSimilar levelHard
- Find Each Customer's Most Recent OrderSimilar levelHard
Keep learning
- Lesson: Window Functions
- Lesson: SQL Subqueries
- Lesson: WHERE Clause
- All SQL practice challenges, by difficulty and topic
- SQL interview questions with answers
- SQL Playground: run any query on the same database