Top 3 Users per Country
Find top 3 users per country by order count.
The challenge runs on the SQLabHub practice database (SQLite) and uses the users and orders tables. You can solve it in the browser, with nothing to install.
The task
Find top 3 users per country by order count.
A correct answer returns 24 rows with 4 columns: country, user_id, cnt, rn.
Tables used in this challenge
users 150 rows
id INTEGER (PK) · first_name TEXT · last_name TEXT · email TEXT · phone TEXT · city TEXT · country TEXT · created_at TEXT · status TEXT · is_premium INTEGER
| id | first_name | last_name | phone | city | country | created_at | status | is_premium | |
|---|---|---|---|---|---|---|---|---|---|
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
| country | user_id | cnt | rn |
|---|---|---|---|
First 5 of 24 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 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
- 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
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
userstable. - Join
ordersonusers.id=orders.user_id. - Group the rows by
users.countryandorders.user_id, so the result has one row for each combination. - For each group, compute
COUNT(*). - Number the rows with
ROW_NUMBER(), ordered byCOUNT(*)descending, restarting for eachusers.country.
- Read from the
- Filter in
WHERE: keep the rows wherernis at most 3. 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
- 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.
Related SQL challenges
- Find the Top-Spending Customer in Each CountrySimilar levelHard
- Find the Top 2 Products by Revenue in Each CategorySimilar levelHard
- Count Orders per Customer per Day with a Two-Column GROUP BYEasierMedium
- Find Each Customer's Largest OrderSimilar levelHard
- Find Each Customer's First OrderSimilar levelHard
Keep learning
- Lesson: ROW_NUMBER()
- 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