SELECT with Snowflake functions - Step-by-Step Execution

Process Flow - SELECT with Snowflake functions

Start Query

↓

Parse SELECT statement

↓

Evaluate each function in SELECT

↓

Fetch data rows

↓

Apply functions to each row

↓

Return transformed results

↓

End Query

The query starts by parsing the SELECT statement, then evaluates each Snowflake function on the data rows, and finally returns the transformed results.

Execution Sample

Snowflake

SELECT UPPER(name), LENGTH(name) FROM users;

This query selects the uppercase version of 'name' and its length from the 'users' table.

Process Table

Step	Action	Input	Function Evaluated	Output
1	Parse SELECT statement	SELECT UPPER(name), LENGTH(name) FROM users;	N/A	Parsed successfully
2	Fetch first row	name='alice'	N/A	Row fetched
3	Apply UPPER(name)	alice	UPPER	ALICE
4	Apply LENGTH(name)	alice	LENGTH	5
5	Return transformed row	N/A	N/A	['ALICE', 5]
6	Fetch second row	name='bob'	N/A	Row fetched
7	Apply UPPER(name)	bob	UPPER	BOB
8	Apply LENGTH(name)	bob	LENGTH	3
9	Return transformed row	N/A	N/A	['BOB', 3]
10	No more rows	N/A	N/A	Query ends

💡 All rows processed, query execution complete

Status Tracker

Variable	Start	After 1	After 2	Final
name	N/A	alice	bob	N/A
UPPER(name)	N/A	ALICE	BOB	N/A
LENGTH(name)	N/A	5	3	N/A

Key Moments - 3 Insights

Why does the function UPPER(name) output 'ALICE' when the input is 'alice'?

Because the UPPER function converts all letters in the input string to uppercase, as shown in execution_table rows 3 and 7.

What happens when there are no more rows to process?

The query ends as indicated in execution_table row 10, stopping further function evaluations.

Are functions applied before or after fetching each row?

Functions are applied after fetching each row, as seen in execution_table where row fetching happens before function application.

Visual Quiz - 3 Questions

Look at the execution table, what is the output of LENGTH(name) at step 8?

A 5

B 3

C BOB

D alice

💡 Hint

Check the 'Output' column at step 8 in the execution_table.

At which step does the query finish processing all rows?

A Step 5

B Step 9

C Step 10

D Step 3

💡 Hint

Look for the step with 'Query ends' in the 'Output' column.

If the input name was 'charlie', what would UPPER(name) output?

A CHARLIE

B charlie

C 7

D char

💡 Hint

Refer to how UPPER transforms 'alice' to 'ALICE' in the variable_tracker.

Concept Snapshot

SELECT with Snowflake functions:
- Use SELECT to choose columns and apply functions.
- Functions like UPPER() and LENGTH() transform data per row.
- Query fetches rows, applies functions, returns results.
- Functions run after data retrieval, per row.
- Query ends when no rows remain.

Full Transcript

This visual execution traces a Snowflake SELECT query using functions. The query selects the uppercase version and length of the 'name' column from the 'users' table. First, the query is parsed. Then each row is fetched one by one. For each row, the UPPER function converts the name to uppercase, and LENGTH calculates the string length. The transformed row is returned. This repeats until all rows are processed, then the query ends. Variables like 'name', 'UPPER(name)', and 'LENGTH(name)' change values as rows are processed. Key moments include understanding when functions apply and when the query stops. The quiz tests understanding of outputs at specific steps and function behavior.

Practice

1. What does the COUNT(*) function do in a Snowflake SELECT query?

easy

A. Calculates the sum of all numeric values in a column

B. Counts only rows with non-null values in a specific column

C. Counts all rows in the selected table or result set

D. Formats a date value into a string

Solution

1. Step 1: Understand COUNT(*) function

   The COUNT(*) counts every row regardless of nulls or values.

2. Step 2: Compare with other options

   Options B, C, and D describe different functions like COUNT(column), SUM(), and TO_CHAR().

3. Final Answer:

   Counts all rows in the selected table or result set -> Option C

4. Quick Check:

   COUNT(*) counts all rows [OK]

Hint: COUNT(*) counts every row, no matter what [OK]

Common Mistakes:

• Confusing COUNT(*) with COUNT(column)
• Thinking COUNT(*) ignores nulls
• Mixing COUNT with SUM or TO_CHAR

2. Which of the following is the correct syntax to convert a date column order_date to a string in format 'YYYY-MM-DD' using Snowflake?

easy

A. SELECT FORMAT_DATE(order_date, 'YYYY-MM-DD') FROM orders;

B. SELECT TO_CHAR(order_date, 'YYYY-MM-DD') FROM orders;

C. SELECT TO_STRING(order_date, 'YYYY-MM-DD') FROM orders;

D. SELECT CAST(order_date AS STRING, 'YYYY-MM-DD') FROM orders;

Solution

1. Step 1: Identify the correct function for date to string

   Snowflake uses TO_CHAR() to format dates as strings.

2. Step 2: Check syntax correctness

   SELECT TO_CHAR(order_date, 'YYYY-MM-DD') FROM orders; uses TO_CHAR(order_date, 'YYYY-MM-DD'), which is correct syntax. Others use invalid or non-existent functions.

3. Final Answer:

   SELECT TO_CHAR(order_date, 'YYYY-MM-DD') FROM orders; -> Option B

4. Quick Check:

   TO_CHAR formats dates to strings [OK]

Hint: Use TO_CHAR to format dates as strings [OK]

Common Mistakes:

• Using TO_STRING instead of TO_CHAR
• Trying FORMAT_DATE which doesn't exist in Snowflake
• Incorrect CAST syntax for formatting

3. Given the table sales with column amount, what is the result of this query?

SELECT SUM(amount) FROM sales WHERE amount > 100;

medium

A. Sum of amounts greater than 100

B. Average of amounts greater than 100

C. Count of rows where amount is greater than 100

D. Sum of all amounts including those less or equal to 100

Solution

1. Step 1: Understand the WHERE clause effect

   The WHERE clause filters rows to only those with amount > 100.

2. Step 2: Understand SUM function

   SUM adds all values of amount from the filtered rows.

3. Final Answer:

   Sum of amounts greater than 100 -> Option A

4. Quick Check:

   SUM with WHERE filters sums filtered rows [OK]

Hint: WHERE filters rows before SUM calculation [OK]

Common Mistakes:

• Including amounts less or equal to 100
• Confusing SUM with COUNT or AVG
• Ignoring WHERE clause effect

4. What is wrong with this Snowflake query?

SELECT TO_CHAR(order_date, YYYY-MM-DD) FROM orders;

medium

A. The date format string is not enclosed in quotes

B. TO_CHAR cannot be used on dates

C. Missing FROM clause

D. TO_CHAR requires three arguments

Solution

1. Step 1: Check TO_CHAR syntax

   The format string must be enclosed in single quotes, like 'YYYY-MM-DD'.

2. Step 2: Identify the error in the query

   The query uses YYYY-MM-DD without quotes, causing a syntax error.

3. Final Answer:

   The date format string is not enclosed in quotes -> Option A

4. Quick Check:

   Format strings need quotes in TO_CHAR [OK]

Hint: Always quote format strings in TO_CHAR [OK]

Common Mistakes:

• Forgetting quotes around format strings
• Thinking TO_CHAR needs more arguments
• Ignoring syntax errors from missing quotes

5. You want to find the average order amount rounded to 2 decimal places from the orders table. Which query correctly achieves this in Snowflake?

hard

A. SELECT AVG(ROUND(order_amount, 2)) FROM orders;

B. SELECT AVG(CAST(order_amount AS NUMBER(10,2))) FROM orders;

C. SELECT TO_CHAR(AVG(order_amount), '0.00') FROM orders;

D. SELECT ROUND(AVG(order_amount), 2) FROM orders;

Solution

1. Step 1: Understand rounding average correctly

   Rounding the average after calculating it gives the correct average rounded to 2 decimals.

2. Step 2: Analyze each option

   SELECT ROUND(AVG(order_amount), 2) FROM orders; rounds the AVG result, which is correct. SELECT AVG(ROUND(order_amount, 2)) FROM orders; rounds each value before averaging, which changes the result. SELECT TO_CHAR(AVG(order_amount), '0.00') FROM orders; converts to string, not numeric. SELECT AVG(CAST(order_amount AS NUMBER(10,2))) FROM orders; casts each value before averaging, which changes the result.

3. Final Answer:

   SELECT ROUND(AVG(order_amount), 2) FROM orders; -> Option D

4. Quick Check:

   Round after AVG for correct decimal rounding [OK]

Hint: Round the average, not individual values [OK]

Common Mistakes:

• Rounding before averaging changes results
• Using TO_CHAR instead of numeric rounding
• Casting individuals before averaging changes results