WITH clause syntax in SQL

Introduction

The WITH clause helps you organize complex queries by creating temporary named results you can use inside your main query.

When you want to break a big query into smaller, easier parts.

When you need to reuse the same subquery multiple times in one query.

When you want to improve readability of your SQL code.

When you want to avoid repeating the same calculation or filtering in multiple places.

When you want to write queries step-by-step like a recipe.

Syntax

SQL

WITH temporary_name AS (
  subquery
)
SELECT columns FROM temporary_name;

The WITH clause defines a temporary named result called a Common Table Expression (CTE).

You can have multiple CTEs separated by commas before the main SELECT.

Examples

This example creates a temporary table named recent_orders with orders after January 1, 2024, then selects all from it.

SQL

WITH recent_orders AS (
  SELECT * FROM orders WHERE order_date > '2024-01-01'
)
SELECT * FROM recent_orders;

This example uses two CTEs: one to sum sales by product, another to get product names, then joins them.

SQL

WITH sales AS (
  SELECT product_id, SUM(amount) AS total_sales FROM orders GROUP BY product_id
),
products AS (
  SELECT id, name FROM products
)
SELECT p.name, s.total_sales
FROM sales s
JOIN products p ON s.product_id = p.id;

Sample Program

This query finds customers who spent more than 1000 in total orders and lists their IDs and total spent.

SQL

WITH high_value_customers AS (
  SELECT customer_id, SUM(total) AS total_spent
  FROM orders
  GROUP BY customer_id
  HAVING SUM(total) > 1000
)
SELECT customer_id, total_spent FROM high_value_customers;

Important Notes

CTEs exist only during the execution of the query; they do not create permanent tables.

You can reference CTEs multiple times in the main query for clarity and efficiency.

Not all databases support recursive CTEs, but many support basic WITH clauses.

Summary

WITH clause creates temporary named results called CTEs.

CTEs help simplify and organize complex queries.

You can use multiple CTEs separated by commas before the main query.

Practice

1. What is the main purpose of the WITH clause in SQL?

easy

A. To create temporary named result sets called Common Table Expressions (CTEs)

B. To permanently store data in a new table

C. To delete rows from a table

D. To update values in a table

Solution

1. Step 1: Understand the role of WITH clause

   The WITH clause defines temporary named result sets called CTEs that exist only during query execution.

2. Step 2: Compare options with WITH clause purpose

   Options B, C, and D describe permanent or data modification actions, which are not the purpose of WITH.

3. Final Answer:

   To create temporary named result sets called Common Table Expressions (CTEs) -> Option A

4. Quick Check:

   WITH clause = Temporary named results [OK]

Hint: WITH clause defines temporary named queries [OK]

Common Mistakes:

• Thinking WITH creates permanent tables
• Confusing WITH with data modification commands
• Assuming WITH is used for deleting or updating data

2. Which of the following is the correct syntax to start a query using a single CTE named cte_example?

easy

A. CREATE cte_example AS (SELECT * FROM table_name); SELECT * FROM cte_example;

B. WITH (SELECT * FROM table_name) AS cte_example SELECT * FROM cte_example;

C. WITH cte_example AS (SELECT * FROM table_name) SELECT * FROM cte_example;

D. SELECT * FROM cte_example WITH (SELECT * FROM table_name);

Solution

1. Step 1: Recall correct WITH clause syntax

   The correct syntax is: WITH cte_name AS (subquery) followed by the main SELECT using cte_name.

2. Step 2: Check each option's syntax

   WITH cte_example AS (SELECT * FROM table_name) SELECT * FROM cte_example; matches the correct syntax. The other options misuse keywords or order.

3. Final Answer:

   WITH cte_example AS (SELECT * FROM table_name) SELECT * FROM cte_example; -> Option C

4. Quick Check:

   WITH cte_name AS (query) SELECT ... [OK]

Hint: WITH cte_name AS (query) SELECT ... is correct syntax [OK]

Common Mistakes:

• Using CREATE instead of WITH for CTE
• Placing AS after the subquery instead of after CTE name
• Misordering clauses in the query

3. Given the following SQL query, what will be the output?

WITH numbers AS (SELECT 1 AS num UNION ALL SELECT 2 UNION ALL SELECT 3) SELECT SUM(num) FROM numbers;

medium

A. 1

B. 3

C. Syntax error

D. 6

Solution

1. Step 1: Understand the CTE content

   The CTE named 'numbers' contains rows with values 1, 2, and 3.

2. Step 2: Calculate the SUM of num column

   Sum of 1 + 2 + 3 equals 6.

3. Final Answer:

   6 -> Option D

4. Quick Check:

   1 + 2 + 3 = 6 [OK]

Hint: Sum values inside CTE to get result [OK]

Common Mistakes:

• Assuming UNION ALL removes duplicates
• Confusing SUM with COUNT
• Expecting syntax error due to CTE

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

WITH cte1 AS SELECT * FROM employees SELECT * FROM cte1;

medium

A. CTE name cannot be cte1

B. Missing parentheses around the CTE's SELECT statement

C. SELECT * FROM cte1 should come before WITH clause

D. WITH clause cannot be used with SELECT

Solution

1. Step 1: Check CTE syntax

   The CTE definition must have parentheses around the SELECT query: AS (SELECT ...)

2. Step 2: Identify missing parentheses

   The query misses parentheses after AS, causing syntax error.

3. Final Answer:

   Missing parentheses around the CTE's SELECT statement -> Option B

4. Quick Check:

   CTE query must be in parentheses [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 have restrictions beyond naming rules

5. Consider this SQL query using multiple CTEs:

WITH cte1 AS (SELECT id, salary FROM employees WHERE department = 'Sales'), cte2 AS (SELECT id, bonus FROM bonuses) SELECT cte1.id, cte1.salary, cte2.bonus FROM cte1 LEFT JOIN cte2 ON cte1.id = cte2.id;

What is the purpose of using multiple CTEs here?

hard

A. To organize complex queries by separating filtering and joining steps

B. To permanently store intermediate results in the database

C. To speed up query execution by caching results automatically

D. To avoid using JOINs by combining data in CTEs

Solution

1. Step 1: Analyze the role of each CTE

   cte1 filters employees in Sales with id and salary; cte2 selects bonuses by id.

2. Step 2: Understand the main query usage

   The main query joins these CTEs to combine salary and bonus data for Sales employees.

3. Step 3: Identify why multiple CTEs are used

   Using multiple CTEs organizes the query into clear steps: filtering and joining, improving readability.

4. Final Answer:

   To organize complex queries by separating filtering and joining steps -> Option A

5. Quick Check:

   Multiple CTEs = Organize complex queries [OK]

Hint: Use multiple CTEs to break complex queries into parts [OK]

Common Mistakes:

• Thinking CTEs store data permanently
• Assuming CTEs automatically speed up queries
• Believing CTEs replace JOINs entirely