Why CTEs are needed in SQL - See It in Action

Understanding Why CTEs Are Needed

📖 Scenario: You are working with a sales database that tracks orders and customers. You want to find customers who have placed more than 2 orders and also want to see their total order count.

🎯 Goal: Build a SQL query using a Common Table Expression (CTE) to first calculate the number of orders per customer, then select only those customers with more than 2 orders.

📋 What You'll Learn

Create a CTE named CustomerOrders that counts orders per customer

Use the CTE to select customers with order count greater than 2

Include customer ID and order count in the final output

💡 Why This Matters

🌍 Real World

CTEs are used in real business reports to simplify complex data queries, making it easier to analyze customer behavior and sales trends.

💼 Career

Knowing how to use CTEs is important for data analysts and database developers to write clear, maintainable, and efficient SQL queries.

1

Create the base table Orders

Create a table called Orders with columns OrderID (integer) and CustomerID (integer). Insert these exact rows: (1, 101), (2, 102), (3, 101), (4, 103), (5, 101), (6, 102).

SQL

-- Create the Orders table and insert data
-- Your code here

Hint

Use CREATE TABLE to define the table and INSERT INTO to add rows.

2

Define the CTE CustomerOrders

Write a CTE named CustomerOrders that selects CustomerID and counts OrderID as OrderCount from Orders, grouping by CustomerID.

SQL

CREATE TABLE Orders (OrderID INT, CustomerID INT);
INSERT INTO Orders (OrderID, CustomerID) VALUES
(1, 101), (2, 102), (3, 101), (4, 103), (5, 101), (6, 102);

WITH CustomerOrders AS (
    -- Your code here
)

Hint

Use WITH to start the CTE and GROUP BY CustomerID to count orders per customer.

3

Use the CTE to filter customers

After the CTE, write a query that selects CustomerID and OrderCount from CustomerOrders where OrderCount is greater than 2.

SQL

CREATE TABLE Orders (OrderID INT, CustomerID INT);
INSERT INTO Orders (OrderID, CustomerID) VALUES
(1, 101), (2, 102), (3, 101), (4, 103), (5, 101), (6, 102);

WITH CustomerOrders AS (
    SELECT CustomerID, COUNT(OrderID) AS OrderCount
    FROM Orders
    GROUP BY CustomerID
)
SELECT CustomerID, OrderCount
FROM CustomerOrders
WHERE -- Your code here

Hint

Use WHERE OrderCount > 2 to filter customers with more than 2 orders.

4

Complete the query with ordering

Add an ORDER BY OrderCount DESC clause to the query to show customers with the highest order counts first.

SQL

CREATE TABLE Orders (OrderID INT, CustomerID INT);
INSERT INTO Orders (OrderID, CustomerID) VALUES
(1, 101), (2, 102), (3, 101), (4, 103), (5, 101), (6, 102);

WITH CustomerOrders AS (
    SELECT CustomerID, COUNT(OrderID) AS OrderCount
    FROM Orders
    GROUP BY CustomerID
)
SELECT CustomerID, OrderCount
FROM CustomerOrders
WHERE OrderCount > 2
-- Your code here

Hint

Use ORDER BY OrderCount DESC to sort results from highest to lowest.

Practice

1. Why do we use Common Table Expressions (CTEs) in SQL queries?

easy

A. To speed up the database server hardware

B. To break complex queries into simpler, readable parts

C. To store data permanently like tables

D. To create indexes automatically

Solution

1. Step 1: Understand the purpose of CTEs

   CTEs help organize complex SQL queries by dividing them into smaller, manageable parts.

2. Step 2: Compare other options

   Options B, C, and D describe unrelated database functions like hardware speed, permanent storage, and indexing, which are not the purpose of CTEs.

3. Final Answer:

   To break complex queries into simpler, readable parts -> Option B

4. Quick Check:

   CTEs simplify queries = A [OK]

Hint: CTEs make big queries easier to read and manage [OK]

Common Mistakes:

• Thinking CTEs improve hardware speed
• Confusing CTEs with permanent tables
• Assuming CTEs create indexes automatically

2. Which of the following is the correct syntax to start a CTE in SQL?

easy

A. WITH cte_name AS (SELECT * FROM table_name)

B. CREATE CTE cte_name SELECT * FROM table_name

C. DEFINE cte_name AS SELECT * FROM table_name

D. START CTE cte_name (SELECT * FROM table_name)

Solution

1. Step 1: Recall standard CTE syntax

   The correct way to define a CTE is using the WITH keyword followed by the CTE name and AS, then the query in parentheses.

2. Step 2: Check other options for syntax errors

   Options A, C, and D use incorrect keywords like CREATE, DEFINE, or START which are not valid for CTEs.

3. Final Answer:

   WITH cte_name AS (SELECT * FROM table_name) -> Option A

4. Quick Check:

   CTE starts with WITH ... AS (...) = B [OK]

Hint: CTEs always start with WITH keyword [OK]

Common Mistakes:

• Using CREATE instead of WITH
• Omitting AS keyword
• Not enclosing query in parentheses

3. Given the query:
WITH SalesCTE AS (SELECT salesperson, SUM(amount) AS total_sales FROM sales GROUP BY salesperson) SELECT * FROM SalesCTE WHERE total_sales > 1000;
What does this query return?

medium

A. Error because CTE cannot be filtered

B. All sales records with amount greater than 1000

C. Sum of all sales amounts in the sales table

D. Salespersons with total sales greater than 1000

Solution

1. Step 1: Analyze the CTE definition

   The CTE named SalesCTE groups sales by salesperson and calculates total sales per person.

2. Step 2: Understand the main query filter

   The main query selects only those salespersons whose total sales exceed 1000.

3. Final Answer:

   Salespersons with total sales greater than 1000 -> Option D

4. Quick Check:

   CTE groups and filters salespersons by total sales > 1000 = A [OK]

Hint: CTEs can be filtered in main query like tables [OK]

Common Mistakes:

• Thinking it returns individual sales over 1000
• Assuming it sums all sales without grouping
• Believing CTEs cannot be filtered

4. Identify the error in this SQL query using a CTE:

WITH cte AS SELECT id, name FROM users SELECT * FROM cte;

medium

A. Missing parentheses around the CTE query

B. CTE name cannot be 'cte'

C. SELECT * FROM cte should come before WITH clause

D. No error, query is correct

Solution

1. Step 1: Check CTE syntax

   The CTE query must be enclosed in parentheses after AS keyword.

2. Step 2: Verify query order and naming

   The CTE name 'cte' is valid, and the main SELECT comes after the CTE definition, so no error there.

3. Final Answer:

   Missing parentheses around the CTE query -> Option A

4. Quick Check:

   CTE query must be in parentheses = D [OK]

Hint: Always put CTE query inside parentheses after AS [OK]

Common Mistakes:

• Omitting parentheses around CTE query
• Placing main SELECT before WITH clause
• Thinking CTE names are restricted

5. You want to find all employees who manage themselves directly or indirectly in a company hierarchy stored in a table employees(id, name, manager_id). Why is a recursive CTE needed here?

hard

A. Because recursive CTEs store data permanently for future use

B. Because recursive CTEs automatically create indexes for faster queries

C. Because recursive CTEs can repeatedly join the table to find all levels of management

D. Because recursive CTEs replace the need for GROUP BY clauses

Solution

1. Step 1: Understand the problem of hierarchical queries

   Finding all managers up the chain requires repeatedly joining the table to itself for multiple levels.

2. Step 2: Recognize recursive CTE capability

   Recursive CTEs allow a query to call itself to traverse hierarchical data until all levels are found.

3. Final Answer:

   Because recursive CTEs can repeatedly join the table to find all levels of management -> Option C

4. Quick Check:

   Recursive CTEs handle hierarchical recursion = C [OK]

Hint: Use recursive CTEs for multi-level hierarchical queries [OK]

Common Mistakes:

• Thinking recursive CTEs create indexes
• Confusing recursive CTEs with permanent storage
• Assuming recursive CTEs replace GROUP BY