Having (SQL) explained

A HAVING clause in SQL specifies that an SQL [[Select (SQL)|SELECT]] statement must only return rows where aggregate values meet the specified conditions.

Use

HAVING and [[Where (SQL)|WHERE]] are often confused by beginners, but they serve different purposes. WHERE is taken into account at an earlier stage of a query execution, filtering the rows read from the tables. If a query contains GROUP BY, rows from the tables are grouped and aggregated. After the aggregating operation, HAVING is applied, filtering out the rows that don't match the specified conditions. Therefore, WHERE applies to data read from tables, and HAVING should only apply to aggregated data, which isn't known in the initial stage of a query.

To view the present condition formed by the GROUP BY clause, the HAVING clause is used.

Examples

To return a list of department IDs whose total sales exceeded $1000 on the date of January 1, 2000, along with the sum of their sales on that date:SELECT DeptID, SUM(SaleAmount)FROM SalesWHERE SaleDate = '2000-01-01'GROUP BY DeptIDHAVING SUM(SaleAmount) > 1000

Referring to the sample tables in the Join example, the following query will return the list of departments which have more than 1 employee:

SELECT DepartmentName, COUNT(*) FROM EmployeeJOIN Department ON Employee.DepartmentID = Department.DepartmentID GROUP BY DepartmentNameHAVING COUNT(*) > 1;

HAVING is convenient, but not necessary. Code equivalent to the example above, but without using HAVING, might look like:

SELECT * FROM (SELECT DepartmentName AS deptNam, COUNT(*) AS empCount FROM Employee AS emp JOIN Department AS dept ON emp.DepartmentID = dept.DepartmentID GROUP BY deptNam) AS grpWHERE grp.empCount > 1;

Having (SQL) explained

Use

Examples

External links