EasySQL challenge #3GROUP BYCOUNT

Count Orders by Status with GROUP BY

Count how many orders are in each status and show the most common status first.

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.

Solve This SQL Challenge

The task

Count how many orders exist for each status.

A correct answer returns 6 rows with 2 columns: status, order_count.

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

First 3 rows of the orders table
iduser_idtotaldiscountitem_countstatusorder_dateshipped_dateshipping_cityshipping_country
1432638.110.253cancelled2024-04-24NULLLos AngelesUSA
2829470.195delivered2024-03-152023-04-09ChicagoUSA
3136683.240.082delivered2023-02-152023-07-10Los AngelesUSA

The first rows of each table are shown. See how all the tables relate on the database schema page.

Expected output

Expected output of the challenge
statusorder_count
delivered82
processing28
cancelled27
pending23
shipped21
refunded19

The complete result: 6 rows. This is the output of the model solution on the practice database.

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
  • Sorting the result with ORDER BY

Hint and approach

Try the challenge first. Open these only when you need them.

Show the hint

Use GROUP BY and COUNT(*)

Show the step-by-step approach

How the model solution is built, in the order the database evaluates it:

  1. Read from the orders table.
  2. Group the rows by status, so the result has one row for each value.
  3. For each group, compute COUNT(*).
  4. Sort the result by order_count descending.

Model solution

Checking your session…

What to watch for

Give COUNT(*) an alias and sort by that alias. Every column in the SELECT list that is not inside an aggregate has to appear in GROUP BY.

  • 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.
  • ORDER BY. Without ORDER BY the row order is not guaranteed, even if it looks stable. Rows that tie on the sort columns can come back in any order.
  • Aggregate functions. Aggregates skip NULLs. AVG divides by the number of non-NULL values and COUNT(column) can be smaller than COUNT(*).
Solve This SQL Challenge

Same technique, other tables

More practice on this pattern with different columns:

Keep learning