N026-M1 Tier 2 · Core SQL · medium ecommerce · Brightlane

Return that count in a single column named `qualifying_customers`

Part of Derived Tables (Subqueries in FROM) in SQL

The problem

Brightlane's growth team needs a single figure: the number of customers who have placed three or more orders.

Write a query to return that count in a single column named qualifying_customers.

Assumptions:

  • The orders table contains every order Brightlane has processed.
  • The inner result produces one row per customer with their order count; the outer query narrows that result to qualifying customers and counts them.
  • The output is a single number — the count of customers who survive the per-customer threshold.

Output:

  • A single row with one column, qualifying_customers.
Schema · ecommerce 5 tables
categories
id integer
name text
parent_id? integer
products
id integer
name text
category_id integer
price numeric
stock_qty integer
attributes? jsonb
order_items
id integer
order_id integer
product_id integer
quantity integer
unit_price numeric
customers
id integer
name text
email text
city? text
country text
created_at timestamptz
is_active boolean
orders
id integer
customer_id integer
ordered_at timestamptz
status text
total_amount numeric

Run previews · Check grades

Write a query, then run it to see results here.

Worked solution Try it yourself first
Solution query
SELECT
  COUNT(*) AS qualifying_customers
FROM
  (
    SELECT
      customer_id,
      COUNT(*) AS order_count
    FROM
      orders
    GROUP BY
      customer_id
  ) AS customer_orders
WHERE
  order_count >= 3

The shape

The inner query produces one row per customer with their order count; the outer query filters those rows down to qualifying customers and then counts the survivors. Two stacked aggregations — the second one runs over the result of the first — and the derived table is the seam that makes the stacking explicit.

Clause by clause

  • The inner block computes a per-customer order count:
SELECT customer_id, COUNT(*) AS order_count
FROM orders
GROUP BY customer_id

One row per customer, with order_count as the running tally of their orders. - FROM (...) AS customer_orders materialises that result as a derived table — a real, named source the outer query can read like any other table. - WHERE order_count >= 3 keeps only customers at or above the threshold. The comparison is inclusive: a customer with exactly three orders qualifies. - SELECT COUNT(*) AS qualifying_customers then aggregates the surviving rows. The outer COUNT(*) counts customers, not orders — each row of the derived table is already one customer, so counting rows here is counting qualifying customers. The result is 48.

You practiced an aggregate over the result of an aggregate. The recurring shape: derived tables make two-pass aggregation natural — the inner pass produces one row per customer, the outer pass produces one row total.

How you actually get good at SQL

Reading explains SQL. Writing it, over and over with instant feedback, is what makes you fluent.

That's the whole SQLMaxx loop: 600+ real problems, instant AI feedback, mastery you can actually see, and spaced review that won't let you forget.

A stack of SQL practice problem cards, the top card showing an employees table.
615 problems · 66 concepts

Real problems. Not toy examples.

615 hand-built problems spanning all 66 concepts, from basic SELECTs to window functions, built on real schemas and real business questions, the kind you'll actually get asked on the job. Enough reps to make SQL automatic.

A retro computer showing a SQL query marked correct with a green checkmark.
Instant AI feedback

Write a query. Know if it's right in one second.

No copying an answer and hoping it clicked. The AI grader checks your real query against real data, catches exactly what's wrong, and explains the fix in plain English, like a senior analyst reading over your shoulder on every problem.

A circular mastery progress dial filling from blue to green, the SQLMaxx diamond at its center.
Mastery tracking

Stop guessing whether you actually know it.

SQLMaxx tracks every concept and shows you what you've mastered and what's still shaky. Your skills fill in one concept at a time, so 'I think I get joins' becomes something you can prove.

A SQL query editor circled by a blue return arrow with a clock, scheduled to come back for review.
Spaced review

Learn it once. Keep it for good.

Most of what you learn this week fades by next week. So when a concept comes due for review, SQLMaxx hands you a fresh problem to solve from a blank editor, not a flashcard to re-read. A research-backed spaced-repetition algorithm (FSRS) times each return for right before you'd forget, so your SQL is still there months later, when the interview or the job actually needs it.

Practice, feedback, mastery, review. That's the loop that turns reading into real skill.

Start free

No account, no credit card. Start solving in under a minute.