WHERE vs HAVING mental model in SQL - When to Use Which

The Big Idea

Ever wondered why filtering data before or after grouping changes your results so much?

The Scenario

Imagine you have a big list of sales data in a spreadsheet. You want to find which products sold more than 100 units in total. You try filtering the rows first, then adding up sales, but it's confusing and you keep making mistakes.

The Problem

Manually filtering rows before or after adding totals is tricky. If you filter too early, you miss important data. If you filter too late, you waste time checking every row. It's easy to get wrong results or spend hours fixing errors.

The Solution

Using WHERE and HAVING in SQL helps you filter data at the right time. WHERE filters rows before grouping, so you only work with relevant data. HAVING filters after grouping, so you can pick groups that meet conditions like total sales above 100. This makes your queries clear and correct.

Before vs After

✗ Before

SELECT product, SUM(sales) FROM sales_data WHERE sales > 100 GROUP BY product;

✓ After

SELECT product, SUM(sales) FROM sales_data GROUP BY product HAVING SUM(sales) > 100;

What It Enables

This mental model lets you write precise queries that find exactly the groups or rows you want, saving time and avoiding mistakes.

Real Life Example

A store manager wants to know which products sold more than 100 units last month. Using WHERE and HAVING correctly, they quickly get the list without missing any product or counting wrong totals.

Key Takeaways

WHERE filters rows before grouping.

HAVING filters groups after aggregation.

Using both correctly makes data queries accurate and efficient.