CTE vs subquery vs view decision in SQL - When to Use Which

The Big Idea

What if you could write your data queries once and reuse them easily without mistakes?

The Scenario

Imagine you have a big spreadsheet with many sheets, and you need to find specific data by copying and pasting formulas between sheets manually.

Each time you want to change something, you must redo all the steps carefully.

The Problem

Doing this by hand is slow and easy to mess up.

You might forget to update one formula or paste in the wrong place, causing wrong results.

It's hard to keep track of what you did and fix mistakes.

The Solution

Using CTEs, subqueries, or views in SQL lets you organize your data queries clearly and reuse parts easily.

They help you write cleaner code that is easier to read, update, and maintain.

Before vs After

✗ Before

SELECT * FROM orders WHERE customer_id IN (SELECT id FROM customers WHERE city = 'NY');

✓ After

WITH ny_customers AS (SELECT id FROM customers WHERE city = 'NY') SELECT * FROM orders WHERE customer_id IN (SELECT id FROM ny_customers);

What It Enables

You can build complex data queries step-by-step, making your work faster, clearer, and less error-prone.

Real Life Example

A sales manager wants to see all orders from customers in New York.

Using a CTE or view, they can write the query once and reuse it anytime without rewriting the whole logic.

Key Takeaways

Manual data filtering is slow and error-prone.

CTEs, subqueries, and views organize queries for clarity and reuse.

They make complex data tasks easier and safer to manage.

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