CTE vs subquery vs view decision in SQL

Introduction

We use CTEs, subqueries, and views to organize and reuse parts of our database queries. Choosing the right one helps keep queries clear and efficient.

When you want to break a complex query into smaller, readable parts.

When you need to reuse a query multiple times in one main query.

When you want to save a query for repeated use without rewriting it.

When you want to improve query readability for yourself or others.

When you want to simplify maintenance by separating logic.

Syntax

SQL

-- CTE syntax
WITH cte_name AS (
  SELECT column1, column2
  FROM table_name
  WHERE condition
)
SELECT * FROM cte_name;

-- Subquery syntax
SELECT column1
FROM (
  SELECT column1, column2
  FROM table_name
  WHERE condition
) AS subquery_alias;

-- View creation syntax
CREATE VIEW view_name AS
SELECT column1, column2
FROM table_name
WHERE condition;

CTEs start with WITH and are temporary for one query.

Subqueries are nested SELECT statements inside another query.

Views are saved queries stored in the database for reuse.

Examples

This CTE selects recent orders and then uses them in the main query.

SQL

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

This subquery counts orders per customer and filters those with more than 5 orders.

SQL

SELECT customer_id
FROM (
  SELECT customer_id, COUNT(*) AS order_count
  FROM orders
  GROUP BY customer_id
) AS order_summary
WHERE order_count > 5;

This view saves a query for active customers to use anytime without rewriting.

SQL

CREATE VIEW active_customers AS
SELECT customer_id, customer_name
FROM customers
WHERE status = 'active';

Sample Program

This query uses a CTE to find orders with total amounts over 1000 and then selects their IDs.

SQL

WITH high_value_orders AS (
  SELECT order_id, total_amount
  FROM orders
  WHERE total_amount > 1000
)
SELECT order_id
FROM high_value_orders;

Important Notes

CTEs improve readability but exist only during query execution.

Subqueries can sometimes be less readable if nested deeply.

Views store queries permanently and can simplify repeated tasks.

Summary

CTEs are best for breaking down complex queries temporarily.

Subqueries nest queries inside others for filtering or calculation.

Views save queries in the database for easy reuse.

Practice

1. Which SQL feature is best used to temporarily break down a complex query into simpler parts for easier reading and maintenance?

easy

A. Common Table Expression (CTE)

B. View

C. Subquery

D. Index

Solution

1. Step 1: Understand the purpose of CTEs

   CTEs allow you to define temporary named result sets that can be referenced within a query, making complex queries easier to read and maintain.

2. Step 2: Compare with other options

   Views are permanent saved queries, subqueries are nested queries but can be harder to read, and indexes are for performance, not query structure.

3. Final Answer:

   Common Table Expression (CTE) -> Option A

4. Quick Check:

   Temporary query breakdown = CTE [OK]

Hint: Temporary query parts? Use CTEs [OK]

Common Mistakes:

• Confusing views as temporary structures
• Thinking subqueries improve readability as much as CTEs
• Assuming indexes help with query structure

2. Which of the following is the correct syntax to define a Common Table Expression (CTE) in SQL?

easy

A. CREATE VIEW cte_name AS SELECT * FROM table_name;

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

C. SELECT * FROM (SELECT * FROM table_name) AS cte_name;

D. DEFINE cte_name SELECT * FROM table_name;

Solution

1. Step 1: Recall CTE syntax

   CTEs start with the keyword WITH, followed by the CTE name, AS, and a query in parentheses.

2. Step 2: Check each option

   WITH cte_name AS (SELECT * FROM table_name) SELECT * FROM cte_name; matches the correct syntax. CREATE VIEW cte_name AS SELECT * FROM table_name; is for views, C is a subquery, and D is invalid syntax.

3. Final Answer:

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

4. Quick Check:

   CTE syntax starts with WITH [OK]

Hint: CTE always starts with WITH keyword [OK]

Common Mistakes:

• Using CREATE VIEW syntax for CTE
• Confusing subquery parentheses with CTE
• Using undefined keywords like DEFINE

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

WITH SalesCTE AS (
  SELECT ProductID, SUM(Quantity) AS TotalSold
  FROM Sales
  GROUP BY ProductID
)
SELECT * FROM SalesCTE WHERE TotalSold > 100;

medium

A. Empty result set because SalesCTE is not materialized

B. All products with total quantity sold less than 100

C. Syntax error due to missing GROUP BY

D. All products with total quantity sold greater than 100

Solution

1. Step 1: Analyze the CTE query

   The CTE calculates total quantity sold per product by grouping Sales data by ProductID and summing Quantity.

2. Step 2: Understand the main query filter

   The main query selects rows from SalesCTE where TotalSold is greater than 100, so it returns products with sales over 100 units.

3. Final Answer:

   All products with total quantity sold greater than 100 -> Option D

4. Quick Check:

   CTE filters totals > 100 = correct output [OK]

Hint: CTE output filters rows after aggregation [OK]

Common Mistakes:

• Thinking CTE is not executed or materialized
• Confusing GROUP BY usage
• Assuming syntax error without checking carefully

4. You wrote this SQL query but it throws an error:

SELECT * FROM (
  SELECT id, name FROM users
) AS user_sub WHERE user_sub.age > 30;

What is the most likely cause of the error?

medium

A. The subquery alias 'user_sub' is missing

B. The WHERE clause should be inside the subquery

C. The subquery does not include the 'age' column needed in WHERE

D. Subqueries cannot be used in FROM clause

Solution

1. Step 1: Check subquery columns

   The subquery selects only 'id' and 'name' columns, but the outer query filters on 'age' which is not selected.

2. Step 2: Understand SQL column visibility

   Since 'age' is not in the subquery result, the outer WHERE clause referencing 'age' causes an error.

3. Final Answer:

   The subquery does not include the 'age' column needed in WHERE -> Option C

4. Quick Check:

   Missing column in subquery causes error [OK]

Hint: Ensure subquery selects all columns used outside [OK]

Common Mistakes:

• Forgetting to alias subquery
• Thinking subqueries can't be in FROM
• Moving WHERE inside subquery unnecessarily

5. You want to reuse a complex query frequently in different reports without rewriting it each time. Which SQL feature should you use and why?

hard

A. Create a View because it saves the query in the database for easy reuse.

B. Use a CTE because it is permanent and can be called anytime.

C. Use a subquery because it is stored and optimized by the database.

D. Create an index because it stores the query results for reuse.

Solution

1. Step 1: Understand the need for reuse

   Reusing a complex query multiple times means you want a saved, reusable object in the database.

2. Step 2: Compare features for reuse

   Views are saved queries stored in the database and can be used repeatedly in different reports. CTEs are temporary and exist only during query execution. Subqueries are inline and not stored. Indexes improve performance but do not store queries.

3. Final Answer:

   Create a View because it saves the query in the database for easy reuse. -> Option A

4. Quick Check:

   Persistent reusable query = View [OK]

Hint: Persistent reusable query? Use a View [OK]

Common Mistakes:

• Confusing CTEs as permanent
• Thinking subqueries are stored
• Misunderstanding indexes as query storage