What if you could get complex sales summaries with just one simple query instead of hours of manual work?
Why CASE with aggregate functions in SQL? - Purpose & Use Cases
Imagine you have a big list of sales data on paper. You want to find out how much money was made from different product categories, but only for certain regions. Doing this by hand means flipping through pages, adding numbers, and trying to remember which sales belong where.
Manually adding numbers for each category and region is slow and easy to mess up. You might forget some sales, add the wrong amounts, or mix categories. It's hard to keep track and update when new data arrives.
Using CASE with aggregate functions in SQL lets you quickly group and sum data based on conditions. You write one query that checks each row, decides which category it belongs to, and adds up the amounts automatically. This saves time and avoids mistakes.
Sum sales for category A in region X by adding each sale manually.
SELECT SUM(CASE WHEN category = 'A' AND region = 'X' THEN sales ELSE 0 END) FROM sales_data;
This lets you create powerful summaries and reports that change instantly when your data changes, all with one simple query.
A store manager wants to see total sales for each product category but only for customers in the city. Using CASE with SUM, they get the answer instantly without sorting or filtering papers.
Manual adding is slow and error-prone.
CASE with aggregate functions automates conditional sums.
It makes data summaries fast, accurate, and easy to update.
Practice
SELECT SUM(CASE WHEN status = 'active' THEN 1 ELSE 0 END) FROM users;Solution
Step 1: Understand the CASE inside SUM
The CASE returns 1 for each row where status is 'active', else 0.Step 2: SUM adds all 1s and 0s
SUM counts how many rows have status 'active' by adding 1s.Final Answer:
Counts how many users have status 'active'. -> Option DQuick Check:
SUM(CASE WHEN condition THEN 1 ELSE 0 END) counts matches [OK]
- Thinking SUM adds status values instead of counting
- Confusing ELSE 0 with ELSE NULL
- Assuming it counts non-active users
score is greater than 50 using CASE inside COUNT?Solution
Step 1: Recall COUNT counts non-null values
COUNT counts rows where expression is NOT NULL.Step 2: Use CASE to return 1 for matches, NULL otherwise
CASE WHEN condition THEN 1 END returns 1 or NULL (default ELSE NULL).Final Answer:
SELECT COUNT(CASE WHEN score > 50 THEN 1 END) FROM results; -> Option AQuick Check:
COUNT with CASE returning NULL for no match counts only matches [OK]
- Using ELSE 0 causes COUNT to count all rows
- Omitting WHEN keyword
- Using invalid CASE syntax
sales with columns region and amount, what is the output of this query?SELECT region, SUM(CASE WHEN amount > 100 THEN amount ELSE 0 END) AS big_sales FROM sales GROUP BY region;
Solution
Step 1: Analyze CASE inside SUM
CASE returns amount if > 100, else 0, so only big sales count fully.Step 2: SUM adds these amounts per region
SUM totals amounts > 100 per region, ignoring smaller sales by adding 0.Final Answer:
Sum of sales amounts greater than 100 per region. -> Option BQuick Check:
SUM with CASE filters values conditionally [OK]
- Thinking it counts rows instead of sums amounts
- Ignoring ELSE 0 and expecting NULL filtering
- Confusing greater than with less than
SELECT department, COUNT(CASE department = 'HR' THEN 1 ELSE NULL END) FROM employees GROUP BY department;
Solution
Step 1: Check CASE syntax
CASE requires WHEN before condition; here it's missing.Step 2: Confirm correct syntax
Correct form: CASE WHEN department = 'HR' THEN 1 ELSE NULL END.Final Answer:
Missing WHEN keyword in CASE statement. -> Option AQuick Check:
CASE syntax needs WHEN before condition [OK]
- Omitting WHEN keyword
- Misusing COUNT with CASE
- Incorrect GROUP BY usage
Solution
Step 1: Understand AVG ignores NULLs
AVG calculates average of non-null values only.Step 2: Use CASE to return salary if > 50000, else NULL
This excludes salaries ≤ 50000 from average calculation.Final Answer:
SELECT AVG(CASE WHEN salary > 50000 THEN salary ELSE NULL END) FROM employees; -> Option CQuick Check:
AVG with CASE ELSE NULL excludes unwanted rows [OK]
- Using ELSE 0 includes zeros in average, skewing result
- Omitting WHEN keyword
- Using invalid CASE syntax
Ready to prove it?
Pass the test and this pattern moves unknown
