Why SELECT with Snowflake functions? - Purpose & Use Cases

The Big Idea

What if you could get answers from mountains of data with just one simple question?

The Scenario

Imagine you have a huge spreadsheet with thousands of rows, and you need to find specific information by hand. You open the file, scroll through rows, and try to calculate totals or filter data manually.

The Problem

This manual way is slow and tiring. You might make mistakes while copying numbers or miss important details. It takes a lot of time and effort, especially when data changes often.

The Solution

Using SELECT with Snowflake functions lets you ask the database to quickly find, calculate, or transform data for you. It works like a smart assistant that understands your questions and gives answers instantly.

Before vs After

✗ Before

Open spreadsheet > Scroll > Find data > Calculate totals by hand

✓ After

SELECT SUM(sales) FROM orders WHERE region = 'West';

What It Enables

You can explore and analyze large data sets instantly, making smarter decisions faster.

Real Life Example

A sales manager uses SELECT with Snowflake functions to see total sales by region every day without opening huge files or doing math manually.

Key Takeaways

Manual data handling is slow and error-prone.

SELECT with Snowflake functions automates data retrieval and calculations.

This makes working with big data fast, accurate, and easy.

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