HAVING filters **groups** after aggregation; WHERE filters **rows** before aggregation. **Why order matters**: HAVING operates on aggregated values (SUM, COUNT, AVG) that don't exist until after GROUP BY. Example: SELECT dept, AVG(sal) FROM emp GROUP BY dept HAVING AVG(sal) > 50000. You can't use WHERE AVG(sal) > 50000 because aggregates aren't computed yet. **Logical order**: FROM → WHERE → GROUP BY → HAVING → SELECT → ORDER BY....
The complete answer continues with detailed implementation patterns, architectural trade-offs, and production-grade considerations. It covers performance optimization strategies, common pitfalls to avoid, and real-world examples from companies like Fossil Group. The answer also includes follow-up discussion points that interviewers commonly explore.
Continue Reading the Full Answer
Unlock the complete expert answer with code examples, trade-offs, and pro tips - plus 1,863+ more.
Or upgrade to Platform Pro - $39
Engineers who used these answers got offers at
AmazonDatabricksSnowflakeGoogleMeta
According to DataEngPrep.tech, this is one of the most frequently asked SQL interview questions, reported at 1 company. DataEngPrep.tech maintains a curated database of 1,863+ real data engineering interview questions across 7 categories, verified by industry professionals.