GROUP BY versus SELECT DISTINCT: how do you choose?
PICTURE THIS: DATABASE INDEX
Simple meaning
DISTINCT removes duplicate result rows.
WHY — SQL instead of guessing?
Why interviewers care about SQL:
contrast on SQL, not two memorised paragraphs.
the developer, then one case where picking wrong hurts.
Name the idea, why it exists, then one short example.
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:
- 1Define it
DISTINCT removes duplicate result rows.
- 2GROUP BY clusters rows
to compute aggregates such as COUNT and SUM.
- 3If you are not
aggregating, DISTINCT is clearer
- 4if you need totals
per customer, you must GROUP BY the non-aggregated columns.
- 5Common mistake
What juniors usually get wrong.
- 6Close
When you pick this over the alternative.
EXAMPLE — See it in action
Here's a short line you can speak, broken into clear beats:
Note: Adapt this scaffold to your own project — keep it under 60–90 seconds.
Key takeaway
DISTINCT removes duplicate result rows. GROUP BY clusters rows to compute aggregates such as COUNT and SUM.