Why optimization controls Snowflake costs - See It in Action

Why optimization controls Snowflake costs

📖 Scenario: You are managing a Snowflake data warehouse for a small company. The company wants to keep costs low while running queries efficiently.

🎯 Goal: Build a simple Snowflake setup that shows how optimizing warehouse size and query execution controls costs.

📋 What You'll Learn

Create a Snowflake warehouse with a specific size

Set a cost control variable for maximum credits per hour

Write a query that uses the warehouse efficiently

Configure auto-suspend and auto-resume to save costs

💡 Why This Matters

🌍 Real World

Companies use Snowflake warehouses to run data queries. Optimizing warehouse settings helps control cloud costs while maintaining performance.

💼 Career

Cloud engineers and data analysts must configure warehouses efficiently to balance cost and speed in Snowflake environments.

1

Create a Snowflake warehouse

Write a Snowflake SQL command to create a warehouse named OPTIMIZE_WH with size SMALL.

Snowflake

-- Your code here to create warehouse OPTIMIZE_WH with size SMALL

Hint

Use CREATE WAREHOUSE and specify WAREHOUSE_SIZE = 'SMALL'.

2

Set cost control with max credits per hour

Write a Snowflake SQL command to alter the warehouse OPTIMIZE_WH to set MAX_CLUSTER_COUNT to 1 to control costs.

Snowflake

CREATE WAREHOUSE OPTIMIZE_WH WITH WAREHOUSE_SIZE = 'SMALL';
-- Your code here to set MAX_CLUSTER_COUNT to 1

Hint

Use ALTER WAREHOUSE to set MAX_CLUSTER_COUNT = 1.

3

Write an efficient query using the warehouse

Write a Snowflake SQL query that selects all columns from SALES_DATA using the warehouse OPTIMIZE_WH.

Snowflake

CREATE WAREHOUSE OPTIMIZE_WH WITH WAREHOUSE_SIZE = 'SMALL';
ALTER WAREHOUSE OPTIMIZE_WH SET MAX_CLUSTER_COUNT = 1;
-- Your code here to select all from SALES_DATA using OPTIMIZE_WH

Hint

Use USE WAREHOUSE OPTIMIZE_WH before the query.

4

Configure auto-suspend and auto-resume

Write a Snowflake SQL command to alter the warehouse OPTIMIZE_WH to set AUTO_SUSPEND to 300 seconds and AUTO_RESUME to TRUE.

Snowflake

CREATE WAREHOUSE OPTIMIZE_WH WITH WAREHOUSE_SIZE = 'SMALL';
ALTER WAREHOUSE OPTIMIZE_WH SET MAX_CLUSTER_COUNT = 1;
USE WAREHOUSE OPTIMIZE_WH;
SELECT * FROM SALES_DATA;
-- Your code here to set AUTO_SUSPEND to 300 and AUTO_RESUME to TRUE

Hint

Use ALTER WAREHOUSE to set AUTO_SUSPEND = 300 and AUTO_RESUME = TRUE.

Practice

1. Why does optimizing queries in Snowflake help reduce costs?

easy

A. Because it increases the size of the data stored

B. Because it uses fewer computing resources and runs faster

C. Because it requires more warehouses to run

D. Because it disables auto-suspend on warehouses

Solution

1. Step 1: Understand resource usage in Snowflake

   Snowflake charges based on compute resources used, so less compute means lower cost.

2. Step 2: Link query optimization to resource use

   Optimized queries run faster and scan less data, using fewer resources.

3. Final Answer:

   Because it uses fewer computing resources and runs faster -> Option B

4. Quick Check:

   Optimization reduces compute = lower cost [OK]

Hint: Less compute time means lower cost in Snowflake [OK]

Common Mistakes:

• Thinking more data scanned reduces cost
• Believing bigger warehouses always save money
• Ignoring auto-suspend settings

2. Which Snowflake warehouse setting helps save costs by stopping compute when not in use?

easy

A. Manual scaling

B. Auto-resume

C. Auto-suspend

D. Clustering keys

Solution

1. Step 1: Identify warehouse settings related to cost

   Auto-suspend stops the warehouse after inactivity, saving compute time.

2. Step 2: Differentiate from other options

   Auto-resume starts warehouse automatically but does not save cost alone; clustering keys optimize data but don't stop compute.

3. Final Answer:

   Auto-suspend -> Option C

4. Quick Check:

   Auto-suspend stops compute = saves cost [OK]

Hint: Auto-suspend pauses warehouse to save money [OK]

Common Mistakes:

• Confusing auto-resume with auto-suspend
• Thinking clustering keys stop compute
• Assuming manual scaling always saves cost

3. Given a query scanning 1TB of data on a large warehouse, what happens if clustering reduces scanned data to 100GB?

medium

A. Query runs faster and costs less

B. Query runs faster but costs more

C. Query runs slower and costs more

D. Query runs slower but costs less

Solution

1. Step 1: Understand clustering effect on data scanned

   Clustering reduces data scanned by organizing data, so less data is processed.

2. Step 2: Link data scanned to query speed and cost

   Less data scanned means faster query and lower compute cost.

3. Final Answer:

   Query runs faster and costs less -> Option A

4. Quick Check:

   Less data scanned = faster + cheaper query [OK]

Hint: Less data scanned means faster and cheaper queries [OK]

Common Mistakes:

• Assuming clustering increases cost
• Thinking faster queries cost more
• Ignoring data scanned impact

4. A Snowflake user notices high costs despite small warehouses. What is a likely cause?

medium

A. Queries scan large amounts of unnecessary data

B. Warehouses are set to auto-suspend after 1 minute

C. Clustering keys are properly defined

D. Warehouses are paused when idle

Solution

1. Step 1: Analyze cost factors with small warehouses

   Small warehouses reduce compute size but scanning large data still increases cost.

2. Step 2: Identify inefficient query behavior

   Queries scanning unnecessary data waste compute time and increase cost despite warehouse size.

3. Final Answer:

   Queries scan large amounts of unnecessary data -> Option A

4. Quick Check:

   Unoptimized queries cause high cost even on small warehouses [OK]

Hint: Check data scanned, not just warehouse size [OK]

Common Mistakes:

• Assuming auto-suspend causes high cost
• Believing clustering keys increase cost
• Ignoring query data scanned

5. You want to reduce Snowflake costs for a large dataset queried daily. Which combined approach is best?

hard

A. Use large warehouses with auto-resume and no clustering

B. Use manual scaling and avoid query tuning

C. Disable auto-suspend and run queries on medium warehouses

D. Use small warehouses with auto-suspend and optimize queries with clustering

Solution

1. Step 1: Evaluate warehouse size and auto-suspend

   Small warehouses with auto-suspend save cost by limiting compute time and size.

2. Step 2: Consider query optimization and clustering

   Optimizing queries and clustering reduce data scanned, speeding queries and lowering cost.

3. Step 3: Combine for best cost control

   Using small warehouses with auto-suspend plus query optimization and clustering balances cost and performance.

4. Final Answer:

   Use small warehouses with auto-suspend and optimize queries with clustering -> Option D

5. Quick Check:

   Small warehouse + auto-suspend + clustering = cost control [OK]

Hint: Combine small warehouse, auto-suspend, and clustering for savings [OK]

Common Mistakes:

• Choosing large warehouses without auto-suspend
• Ignoring query optimization
• Disabling auto-suspend increases cost