Study Guide: SQL HAVING Clause
This video explains the SQL HAVING clause, which is used to filter results after aggregation with
GROUP BY. It covers the difference between WHERE and HAVING clauses, proper syntax
placement, and provides practical examples using a customer database.
Key Concepts
HAVING Clause: An SQL clause used to filter the results of aggregate functions (like COUNT,
MAX, MIN, SUM, AVG) after data has been grouped using GROUP BY. It acts as a filter
specifically for aggregated data.
GROUP BY Clause: An SQL clause that groups rows sharing a common value into summary
rows, often used with aggregate functions to perform calculations on each group.
Aggregate Functions: SQL functions that perform calculations on a set of values and return a
single result. Examples include COUNT, MAX, MIN, SUM, and AVG.
WHERE Clause: An SQL clause used to filter data based on columns that already exist in the
database. It filters rows before any grouping or aggregation occurs.
SQL Clause Order: The specific sequence in which SQL clauses must appear in a query:
SELECT, FROM, JOIN, WHERE, GROUP BY, HAVING, ORDER BY, LIMIT.
Main Takeaways
* The HAVING clause must be placed immediately after the GROUP BY clause in your SQL
query.
* Use HAVING when you need to filter based on aggregate function results (COUNT, SUM, MAX,
MIN, AVG).
* Use WHERE when you need to filter based on columns that already exist in the database.
* HAVING only works in conjunction with GROUP BY when performing aggregation operations.
* The HAVING clause is optional and is only needed when you want to filter aggregated results.
* SQL is sensitive to the order of clauses - incorrect placement will cause errors.
Important Facts
* The complete order of SQL clauses is: SELECT → FROM → JOIN → WHERE → GROUP BY
→ HAVING → ORDER BY → LIMIT
* HAVING works exclusively with GROUP BY for filtering aggregated data
* WHERE filters data before grouping occurs; HAVING filters data after grouping and aggregation
* You cannot use WHERE to filter on computed/aggregated columns like COUNT(*) - you must
use HAVING
* The HAVING clause syntax is similar to WHERE - both use conditions, but they operate on
different types of data
Summary
The HAVING clause is an essential SQL tool for filtering grouped and aggregated data. While the
WHERE clause filters individual rows based on existing database columns before any grouping
occurs, HAVING filters the results after GROUP BY has aggregated the data. This distinction is
critical because aggregate functions like COUNT, SUM, MAX, and MIN create computed values that
don't exist as actual columns in the database, making them inaccessible to the WHERE clause. The
HAVING clause must always appear immediately after GROUP BY in the query structure. A practical
example demonstrated in the video involves finding countries with more than one customer: first, the
data is grouped by country with COUNT(*) calculating total customers per country, then HAVING
COUNT(*) > 1 filters out countries with only one customer. Understanding when to use WHERE
versus HAVING is fundamental to writing effective SQL queries that properly filter data at the
appropriate stage of query execution.