N013-E1 Tier 2 · Core SQL · easy ecommerce · Brightlane

Return the total number of orders the platform has processed in a single column named `order_count`

Part of Aggregate Functions (COUNT, SUM, AVG, MIN, MAX) in SQL

The problem

Brightlane's operations team is building a weekly capacity report and needs a baseline order-volume figure.

Write a query to return the total number of orders the platform has processed in a single column named order_count.

Assumptions:

  • The orders table contains every order Brightlane has processed.
  • Every row in orders represents one order; the count is simply the row count.

Output:

  • A single row with one column, order_count, containing the total order count.
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 order_count
FROM
  orders

The shape

COUNT(*) collapses every row of the orders table down to a single number — the total count of orders Brightlane has processed. An aggregate query always returns exactly one row of summary numbers, regardless of how many rows live in the source table.

Clause by clause

  • SELECT COUNT(*) is the aggregate. The * means "every row," so PostgreSQL walks the table, counts rows as it goes, and returns one number. The result row has one column whether the underlying table has zero, three, or three million rows. For this dataset, the count is 200.
  • AS order_count labels that single number as the domain quantity. Without it, the column would come back as count — PostgreSQL's default name for the result of COUNT. The alias makes the result self-documenting: anyone reading the column header knows what was counted.
  • FROM orders is what COUNT(*) reads from. Aggregates always need to know which set of rows to collapse, and the FROM clause provides that set.

You practiced collapsing an entire table to a single number with COUNT(*). The recurring shape: when the question is "how many rows," COUNT(*) reads every row's existence — column values are irrelevant.

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.