Moderate SQL Analytics Question 107 of 220

When is DISTINCT the wrong tool compared with GROUP BY?

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

DISTINCT removes duplicate full rows but does not compute sums, and it can hide that you joined explosively and then deduped.

WHY — SQL Analytics instead of guessing?

Why interviewers care about SQL Analytics:

They are checking judgment

on SQL Analytics.

A good answer names

the situation, the default choice, and one exception - that reads as experience.

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
DISTINCT removes duplicate full
rows but does not compute sums, and it can hide that you joined explosively and then deduped.
2
GROUP BY with aggregates
is the honest way to define metrics at a grain.
3
If you need one
row per user, group on user_id and choose an aggregation rule, not a random remaining row.
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

“GROUP BY with aggregates is the honest way to define metrics at a grain.”

Break into beats

GROUPBYwithaggregatesisthe

Speaking order

2987408337471632900

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

Key takeaway

DISTINCT removes duplicate full rows but does not compute sums, and it can hide that you joined explosively and then deduped. GROUP BY with aggregates is the honest way to define metrics at a grain.