Warehouse selection strategies in Snowflake - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to select a warehouse for running a query.

Snowflake

USE WAREHOUSE [1];

Drag options to blanks, or click blank then click option'

ACOMPUTE_WH

BANALYTICS_WH

CDEFAULT_WH

DDATA_WH

Attempts:

3 left

💡 Hint

Common Mistakes

Using a warehouse name that does not exist.

Forgetting to use the USE WAREHOUSE command before running queries.

The USE WAREHOUSE command sets the active warehouse. Here, DATA_WH is the correct warehouse name to select.

2fill in blank

medium

Complete the code to create a warehouse with a specific size.

Snowflake

CREATE WAREHOUSE my_wh WAREHOUSE_SIZE = '[1]';

Drag options to blanks, or click blank then click option'

AXSMALL

BLARGE

CMEDIUM

DXLARGE

Attempts:

3 left

💡 Hint

Common Mistakes

Using lowercase size names which are invalid.

Using sizes not supported by Snowflake.

The WAREHOUSE_SIZE parameter defines the size of the warehouse. MEDIUM is a valid size option.

3fill in blank

hard

Fix the error in the warehouse auto-suspend configuration.

Snowflake

ALTER WAREHOUSE my_wh SET AUTO_SUSPEND = [1];

Drag options to blanks, or click blank then click option'

A300

B'300'

C'off'

Doff

Attempts:

3 left

💡 Hint

Common Mistakes

Putting the number in quotes, making it a string.

Using the string 'off' instead of 0 to disable.

The AUTO_SUSPEND parameter expects an integer number of seconds. The correct value is 300 without quotes.

4fill in blank

hard

Fill both blanks to create a warehouse with multi-cluster enabled and set minimum clusters.

Snowflake

CREATE WAREHOUSE multi_wh [1] = TRUE MIN_CLUSTER_COUNT = [2];

Drag options to blanks, or click blank then click option'

AMULTI_CLUSTER_WAREHOUSE

BMAX_CLUSTER_COUNT

CMIN_CLUSTER_COUNT

DAUTO_SUSPEND

Attempts:

3 left

💡 Hint

Common Mistakes

Confusing MAX_CLUSTER_COUNT with MIN_CLUSTER_COUNT.

Not enabling MULTI_CLUSTER_WAREHOUSE before setting cluster counts.

MULTI_CLUSTER_WAREHOUSE enables multi-cluster warehouses. MIN_CLUSTER_COUNT sets the minimum number of clusters.

5fill in blank

hard

Fill all three blanks to alter a warehouse to set auto-resume, size, and max clusters.

Snowflake

ALTER WAREHOUSE my_wh SET AUTO_RESUME = [1], WAREHOUSE_SIZE = '[2]', MAX_CLUSTER_COUNT = [3];

Drag options to blanks, or click blank then click option'

ATRUE

BLARGE

C5

DFALSE

Attempts:

3 left

💡 Hint

Common Mistakes

Using FALSE for AUTO_RESUME when auto-resume is desired.

Not quoting the warehouse size string.

Setting MAX_CLUSTER_COUNT to a string instead of a number.

AUTO_RESUME should be set to TRUE to resume automatically. WAREHOUSE_SIZE is set to LARGE. MAX_CLUSTER_COUNT is set to 5 to limit clusters.

Practice

1. What does the USE WAREHOUSE command do in Snowflake?

easy

A. It lists all available warehouses.

B. It switches the current warehouse to run queries.

C. It deletes an existing warehouse.

D. It creates a new warehouse.

Solution

1. Step 1: Understand the purpose of USE WAREHOUSE

   This command changes which warehouse is active for running queries.

2. Step 2: Compare with other commands

   Creating, deleting, or listing warehouses use different commands, not USE WAREHOUSE.

3. Final Answer:

   It switches the current warehouse to run queries. -> Option B

4. Quick Check:

   USE WAREHOUSE changes active warehouse [OK]

Hint: Remember: USE means switch active warehouse [OK]

Common Mistakes:

• Confusing USE with CREATE or DROP commands
• Thinking it lists warehouses
• Assuming it modifies warehouse size

2. Which of the following is the correct syntax to switch to a warehouse named COMPUTE_WH?

easy

A. USE WAREHOUSE COMPUTE_WH;

B. SWITCH WAREHOUSE COMPUTE_WH;

C. SELECT WAREHOUSE COMPUTE_WH;

D. CHANGE WAREHOUSE TO COMPUTE_WH;

Solution

1. Step 1: Recall the correct command syntax

   The command to switch warehouses is USE WAREHOUSE <name>;.

2. Step 2: Check each option

   Only USE WAREHOUSE COMPUTE_WH; matches the correct syntax exactly.

3. Final Answer:

   USE WAREHOUSE COMPUTE_WH; -> Option A

4. Quick Check:

   Correct syntax = USE WAREHOUSE [name]; [OK]

Hint: USE WAREHOUSE plus name switches warehouse [OK]

Common Mistakes:

• Using SWITCH or CHANGE instead of USE
• Adding extra keywords like TO or SELECT
• Missing semicolon at end

3. Given the following commands run in order:

USE WAREHOUSE SMALL_WH;
SELECT CURRENT_WAREHOUSE();
USE WAREHOUSE LARGE_WH;
SELECT CURRENT_WAREHOUSE();

What will be the output of the two CURRENT_WAREHOUSE() calls?

medium

A. SMALL_WH then LARGE_WH

B. LARGE_WH then SMALL_WH

C. SMALL_WH twice

D. LARGE_WH twice

Solution

1. Step 1: Analyze the first USE WAREHOUSE command

   The first command sets the active warehouse to SMALL_WH, so the first CURRENT_WAREHOUSE() returns SMALL_WH.

2. Step 2: Analyze the second USE WAREHOUSE command

   The second command switches the active warehouse to LARGE_WH, so the second CURRENT_WAREHOUSE() returns LARGE_WH.

3. Final Answer:

   SMALL_WH then LARGE_WH -> Option A

4. Quick Check:

   Warehouse switches reflect in CURRENT_WAREHOUSE() [OK]

Hint: Each USE WAREHOUSE changes current warehouse immediately [OK]

Common Mistakes:

• Assuming warehouse does not change after second USE
• Mixing order of outputs
• Thinking CURRENT_WAREHOUSE() returns session name

4. You run the command USE WAREHOUSE BIG_WH but get an error saying the warehouse does not exist. What is the most likely cause?

medium

A. The command requires a semicolon at the end.

B. You need to restart your Snowflake session.

C. You must create a database before switching warehouses.

D. The warehouse name is misspelled or does not exist.

Solution

1. Step 1: Understand the error message

   The error says the warehouse does not exist, so the name is likely wrong or missing.

2. Step 2: Evaluate other options

   Restarting session or creating a database is unrelated; semicolon missing usually causes syntax error, not 'does not exist'.

3. Final Answer:

   The warehouse name is misspelled or does not exist. -> Option D

4. Quick Check:

   Nonexistent warehouse name causes error [OK]

Hint: Check warehouse name spelling if 'does not exist' error appears [OK]

Common Mistakes:

• Restarting session unnecessarily
• Confusing warehouse with database
• Ignoring error message details

5. You have two warehouses: SMALL_WH with 1 cluster and LARGE_WH with 4 clusters. You want to run a heavy query quickly but also save costs on light queries. Which strategy is best?

hard

A. Always use LARGE_WH for all queries to ensure speed.

B. Use SMALL_WH only and increase its size when needed.

C. Use SMALL_WH for light queries and switch to LARGE_WH for heavy queries.

D. Create a new warehouse for each query type.

Solution

1. Step 1: Understand warehouse sizes and costs

   SMALL_WH is cheaper and good for light work; LARGE_WH is bigger and faster but costs more.

2. Step 2: Choose strategy balancing speed and cost

   Switching warehouses based on query load saves cost and improves performance.

3. Final Answer:

   Use SMALL_WH for light queries and switch to LARGE_WH for heavy queries. -> Option C

4. Quick Check:

   Match warehouse size to query load for cost and speed [OK]

Hint: Match warehouse size to query weight, switch as needed [OK]

Common Mistakes:

• Using large warehouse always wastes cost
• Trying to resize warehouses dynamically
• Creating many warehouses unnecessarily