SQL Execution Order Internals: Why WHERE Fails on Aliases but ORDER BY Succeeds

Arpit Bangre — Fri, 28 Aug 2026 07:08:52 +0000

Ever wondered why this query fails in SQL?

SELECT department_id, COUNT(*) AS emp_count
FROM employees
WHERE emp_count > 5 -- ❌ Error: Invalid column name 'emp_count'
GROUP BY department_id;

Because WHERE executes at Stage 2, the emp_count alias created at Stage 5 (SELECT) does not exist in memory yet!

However, ORDER BY runs at Stage 6 (after SELECT), which is why ORDER BY emp_count DESC works seamlessly.

Use HAVING for aggregated filtering:

SELECT department_id, COUNT(*) AS emp_count
FROM employees
GROUP BY department_id
HAVING COUNT(*) > 5;

💡 What's your favorite SQL execution order quirk? Drop your thoughts below!

DEV Community: Arpit Bangre