Easy SQL Analytics Question 33 of 220

What is the difference between WHERE and HAVING?

Data Science track · Speak this in 60–90 seconds · Faridabad & Delhi NCR

PICTURE THIS: DATABASE INDEX

Without indexScan every row

With indexJump to keys

CostWrites slower

Simple meaning

WHERE filters rows before aggregation, while HAVING filters groups after GROUP BY.

WHY — SQL Analytics instead of guessing?

Why interviewers care about SQL Analytics:

They want a clean

contrast on SQL Analytics, not two memorised paragraphs.

Say what changes for

the developer, then one case where picking wrong hurts.

Stay structured

Name the idea, why it exists, then one short example.

Close cleanly

End with when you use it and one common pitfall.

STEPS — What happens step by step?

Before you speak the answer, walk the interviewer through these steps:

1
WHERE filters rows before
aggregation, while HAVING filters groups after GROUP BY.
2
You cannot reference aggregate
results such as SUM(revenue) in WHERE.
3
Use WHERE for event-level
filters and HAVING for conditions like groups with at least 100 users.
4
Give an example
One tiny concrete case you can say aloud.
5
Common mistake
What juniors usually get wrong.
6
Close
When you pick this over the alternative.

EXAMPLE — See it in action

Here's a short line you can speak, broken into clear beats:

Say this line

“You cannot reference aggregate results such as SUM(revenue) in WHERE.”

Break into beats

Youcannotreferenceaggregateresultssuch

Speaking order

2987408337471632900

Note: Adapt this scaffold to your own project — keep it under 60–90 seconds.

Key takeaway

WHERE filters rows before aggregation, while HAVING filters groups after GROUP BY. You cannot reference aggregate results such as SUM(revenue) in WHERE.