Top 10% Users by Spend
Find users in top 10% by total spend.
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 users in top 10% by total spend.
A correct answer returns 12 rows with 3 columns: user_id, spend, 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
| user_id | spend | bucket |
|---|---|---|
First 5 of 12 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
- 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
- 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(10)
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
user_id, so the result has one row for each value. - For each group, compute
SUM(total). - Deal the rows into 10 equal-sized buckets with
NTILE(10), ordered bySUM(total)descending.
- 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.
- 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
- Find the Top 10% Most Expensive Products with NTILESimilar levelHard
- Split Employees into Salary Quartiles with NTILE(4)Similar levelHard
- Find the Top 5 Customers by Total SpendEasierMedium
- Find Days Where Revenue Rose Twice in a RowSimilar levelHard
- Find the Top-Spending Customer in Each CountrySimilar levelHard
Keep learning
- Lesson: Window Functions
- Lesson: SQL Subqueries
- Lesson: GROUP BY
- Lesson: Aggregate Functions
- All SQL practice challenges, by difficulty and topic
- SQL interview questions with answers
- SQL Playground: run any query on the same database