Common Table Expressions (CTEs) in Snowflake - Time & Space Complexity

Time Complexity: Common Table Expressions (CTEs)

O(n)

Understanding Time Complexity

When using Common Table Expressions (CTEs) in Snowflake, it's important to understand how the time to run queries grows as the data size increases.

We want to know how the number of operations changes when the input data gets bigger.

Scenario Under Consideration

Analyze the time complexity of this CTE query sequence.

WITH recent_orders AS (
  SELECT * FROM orders WHERE order_date >= DATEADD(day, -30, CURRENT_DATE())
),
customer_totals AS (
  SELECT customer_id, SUM(amount) AS total_spent FROM recent_orders GROUP BY customer_id
)
SELECT * FROM customer_totals WHERE total_spent > 1000;
    

This query uses two CTEs: one to filter recent orders, and another to sum spending per customer, then filters customers by total spent.

Identify Repeating Operations

Look at the main operations that happen repeatedly.

• Primary operation: Scanning the orders table and grouping by customer_id.
• How many times: The orders table is scanned once; grouping depends on number of customers in recent orders.

How Execution Grows With Input

As the number of recent orders grows, the scan and grouping take more time.

Input Size (n)	Approx. Api Calls/Operations
10	About 10 rows scanned and grouped
100	About 100 rows scanned and grouped
1000	About 1000 rows scanned and grouped

Pattern observation: The work grows roughly in direct proportion to the number of recent orders.

Final Time Complexity

Time Complexity: O(n)

This means the time to run the query grows linearly with the number of rows processed in the CTE.

Common Mistake

[X] Wrong: "CTEs always run once and do not affect query time as data grows."

[OK] Correct: CTEs are like temporary views; their cost depends on the data size they process, so bigger data means more work.

Interview Connect

Understanding how CTEs impact query time helps you design efficient data pipelines and write queries that scale well.

Self-Check

"What if the CTE included a join with another large table? How would the time complexity change?"

Practice

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

easy

A. To set session variables

B. To permanently store data in a new table

C. To create a user-defined function

D. To define a temporary named result set for use in a query

Solution

1. Step 1: Understand the role of the WITH clause

   The WITH clause defines a Common Table Expression (CTE), which is a temporary named result set used within a query.

2. Step 2: Differentiate from other SQL features

   Unlike permanent tables or functions, CTEs exist only during query execution and help organize complex queries.

3. Final Answer:

   To define a temporary named result set for use in a query -> Option D

4. Quick Check:

   WITH clause = temporary named result set [OK]

Hint: WITH means temporary named query part [OK]

Common Mistakes:

• Thinking WITH creates permanent tables
• Confusing WITH with functions or variables
• Assuming WITH changes session settings

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

easy

A. CREATE CTE cte_name AS (SELECT * FROM table);

B. DEFINE cte_name SELECT * FROM table;

C. WITH cte_name AS (SELECT * FROM table)

D. BEGIN CTE cte_name SELECT * FROM table;

Solution

1. Step 1: Recall the standard CTE syntax

   In Snowflake, a CTE starts with the keyword WITH followed by the CTE name and AS, then the query in parentheses.

2. Step 2: Compare options to syntax

   WITH cte_name AS (SELECT * FROM table) matches this pattern exactly: WITH cte_name AS (SELECT * FROM table)

3. Final Answer:

   WITH cte_name AS (SELECT * FROM table) -> Option C

4. Quick Check:

   CTE syntax starts with WITH [OK]

Hint: CTE always starts with WITH keyword [OK]

Common Mistakes:

• Using CREATE instead of WITH
• Omitting AS keyword
• Using BEGIN or DEFINE which are invalid here

3. Given the query:

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

What is the output of this query?

medium

A. 3

B. 2

C. 1

D. Error

Solution

1. Step 1: Understand the CTE content

   The CTE named 'cte' selects two rows with values 1 and 2 under the column 'num'.

2. Step 2: Calculate the SUM of 'num'

   The main query sums the values 1 and 2, resulting in 3.

3. Final Answer:

   3 -> Option A

4. Quick Check:

   1 + 2 = 3 [OK]

Hint: Sum values inside CTE then add [OK]

Common Mistakes:

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

4. Identify the error in the following Snowflake query using a CTE:

WITH cte AS SELECT * FROM employees SELECT * FROM cte;

medium

A. Missing parentheses around the CTE query

B. CTE name cannot be 'cte'

C. CTE cannot be used in the same query

D. Missing AS keyword before SELECT in CTE definition

Solution

1. Step 1: Review CTE syntax requirements

   A CTE query must be enclosed in parentheses after the AS keyword.

2. Step 2: Check the given query

   The query lacks parentheses around the SELECT statement in the CTE definition.

3. Final Answer:

   Missing parentheses around the CTE query -> Option A

4. Quick Check:

   CTE query must be in parentheses [OK]

Hint: CTE query always inside parentheses [OK]

Common Mistakes:

• Omitting parentheses around CTE query
• Thinking CTE names are restricted
• Believing CTEs can't be reused in same query

5. You want to calculate the average salary per department using a CTE named dept_salaries that selects employee salaries and departments. Which query correctly uses the CTE to get the average salary per department?

hard

A. WITH dept_salaries AS SELECT department, salary FROM employees SELECT department, AVG(salary) FROM dept_salaries GROUP BY department;

B. WITH dept_salaries AS (SELECT department, salary FROM employees) SELECT department, AVG(salary) FROM dept_salaries GROUP BY department;

C. WITH dept_salaries (department, salary) AS (SELECT department, salary FROM employees) SELECT AVG(salary) FROM dept_salaries;

D. WITH dept_salaries AS (SELECT department, salary FROM employees) SELECT AVG(salary) FROM employees GROUP BY department;

Solution

1. Step 1: Verify correct CTE syntax and usage

   WITH dept_salaries AS (SELECT department, salary FROM employees) SELECT department, AVG(salary) FROM dept_salaries GROUP BY department; correctly defines the CTE with parentheses and AS, then uses it to select department and average salary grouped by department.

2. Step 2: Check aggregation and grouping

   WITH dept_salaries AS (SELECT department, salary FROM employees) SELECT department, AVG(salary) FROM dept_salaries GROUP BY department; groups by department and calculates AVG(salary) from the CTE, which is the intended calculation.

3. Final Answer:

   WITH dept_salaries AS (SELECT department, salary FROM employees) SELECT department, AVG(salary) FROM dept_salaries GROUP BY department; -> Option B

4. Quick Check:

   CTE with correct syntax and grouping = WITH dept_salaries AS (SELECT department, salary FROM employees) SELECT department, AVG(salary) FROM dept_salaries GROUP BY department; [OK]

Hint: Use WITH ... AS (...) then GROUP BY correctly [OK]

Common Mistakes:

• Omitting parentheses in CTE definition
• Not grouping by department when aggregating
• Using employees table instead of CTE in main query