Count Distinct Products per Order
Return each order with the number of different products it contains.
The challenge runs on the SQLabHub practice database (SQLite) and uses the order_items table. You can solve it in the browser, with nothing to install.
The task
Find distinct products count per order.
A correct answer returns 200 rows with 2 columns: order_id, COUNT(DISTINCT product_id).
Tables used in this challenge
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
| order_id | COUNT(DISTINCT product_id) |
|---|---|
First 5 of 200 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
- Counting different values with COUNT(DISTINCT …)
- Grouping rows with GROUP BY to get one result row per group
Hint and approach
Try the challenge first. Open these only when you need them.
Show the hint
COUNT DISTINCT
Show the step-by-step approach
How the model solution is built, in the order the database evaluates it:
- Read from the
order_itemstable. - Group the rows by
order_id, so the result has one row for each value. - For each group, compute
COUNT(DISTINCT product_id), which counts each different value once.
Model solution
Checking your session…
What to watch for
COUNT(DISTINCT product_id) counts each product once per order even if it appears on two lines. COUNT(*) would count the lines instead.
- COUNT(DISTINCT). After a join, COUNT(*) counts joined rows. Counting the parent entity needs COUNT(DISTINCT its id).
- 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.
- Aggregate functions. Aggregates skip NULLs. AVG divides by the number of non-NULL values and COUNT(column) can be smaller than COUNT(*).
Related SQL challenges
- Find Orders Containing More Than One ProductSimilar levelMedium
- Calculate Revenue and Units Sold per Product CategorySimilar levelMedium
- Count Orders by Status with GROUP BYEasierEasy
- Count Distinct Products Bought by Each CustomerHarderHard
- Calculate Average Items per Order for Each CustomerHarderHard
Same technique, other tables
More practice on this pattern with different columns:
Keep learning
- Lesson: Aggregate Functions
- Lesson: GROUP BY
- All SQL practice challenges, by difficulty and topic
- SQL interview questions with answers
- SQL Playground: run any query on the same database