Tasks for scheduling SQL in Snowflake - Commands & Configuration

Introduction

Scheduling SQL queries helps automate repetitive database tasks like data updates or reports. Snowflake Tasks let you run SQL statements on a set schedule without manual work.

When you want to refresh a summary table every hour automatically.

When you need to run daily data cleanup jobs without logging in.

When you want to automate sending reports by running queries at night.

When you want to chain multiple SQL commands to run one after another.

When you want to reduce manual errors by automating routine SQL tasks.

Commands

This command creates a task named 'my_hourly_task' that runs every hour at minute 0 using a specified warehouse. It inserts the current timestamp and a count from 'source_table' into 'my_table'.

Terminal

CREATE OR REPLACE TASK my_hourly_task
  WAREHOUSE = my_warehouse
  SCHEDULE = 'USING CRON 0 * * * * UTC'
AS
  INSERT INTO my_table SELECT CURRENT_TIMESTAMP, COUNT(*) FROM source_table;

Expected Output

Task MY_HOURLY_TASK created.

→

WAREHOUSE - Specifies the compute resource to run the task.

→

SCHEDULE - Defines when the task runs using a cron expression.

This command starts the task so it begins running on its schedule.

Terminal

ALTER TASK my_hourly_task RESUME;

Expected Output

Task MY_HOURLY_TASK resumed.

This command shows details about the task to confirm it exists and is active.

Terminal

SHOW TASKS LIKE 'my_hourly_task';

Expected Output

name           | database_name | schema_name | owner | comment | schedule          | state  

MY_HOURLY_TASK | MY_DB        | PUBLIC      | USER  |         | CRON 0 * * * * UTC | started

This command checks the recent run history of the task to see if it executed successfully.

Terminal

SELECT * FROM TABLE(INFORMATION_SCHEMA.TASK_HISTORY()) WHERE NAME = 'MY_HOURLY_TASK' ORDER BY SCHEDULED_TIME DESC LIMIT 5;

Expected Output

NAME           | SCHEDULED_TIME       | STATE   | ERROR

MY_HOURLY_TASK | 2024-06-01 12:00:00 | SUCCEEDED | NULL

MY_HOURLY_TASK | 2024-06-01 11:00:00 | SUCCEEDED | NULL

MY_HOURLY_TASK | 2024-06-01 10:00:00 | SUCCEEDED | NULL

Key Concept

If you remember nothing else from this pattern, remember: Snowflake Tasks automate SQL by running queries on a schedule using a warehouse.

Common Mistakes

Creating a task but forgetting to resume it.

The task stays paused and never runs on schedule.

Always run ALTER TASK task_name RESUME after creating the task.

Using an invalid cron expression in the SCHEDULE clause.

The task creation fails or the schedule does not work as expected.

Use valid cron syntax and test schedules carefully.

Not specifying a warehouse for the task.

The task cannot run because it has no compute resource.

Always specify WAREHOUSE when creating a task.

Summary

Create a task with CREATE TASK specifying warehouse and schedule.

Start the task with ALTER TASK ... RESUME to enable scheduled runs.

Check task status with SHOW TASKS and recent runs with TASK_HISTORY.

Practice

1. What is the main purpose of a TASK in Snowflake?

easy

A. To create user accounts

B. To store large amounts of data

C. To automate running SQL statements on a schedule

D. To manage network security

Solution

1. Step 1: Understand the role of TASK in Snowflake

   A TASK is designed to run SQL commands automatically at set times.

2. Step 2: Compare TASK purpose with other options

   Storing data, creating users, and managing security are handled by other Snowflake features, not TASKS.

3. Final Answer:

   To automate running SQL statements on a schedule -> Option C

4. Quick Check:

   Task = automate SQL schedule [OK]

Hint: Tasks run SQL automatically on schedule [OK]

Common Mistakes:

• Confusing TASK with data storage
• Thinking TASK creates users
• Assuming TASK manages security

2. Which of the following is the correct syntax to create a simple task that runs every hour in Snowflake?

easy

A. CREATE TASK my_task WAREHOUSE = my_wh SCHEDULE = 'USING CRON 0 * * * * UTC' AS SELECT CURRENT_TIMESTAMP();

B. CREATE TASK my_task WAREHOUSE = my_wh SCHEDULE = 'EVERY 1 HOUR' AS SELECT CURRENT_TIMESTAMP();

C. CREATE TASK my_task WAREHOUSE = my_wh SCHEDULE = 'CRON 0 0 * * *' AS SELECT CURRENT_TIMESTAMP();

D. CREATE TASK my_task WAREHOUSE = my_wh SCHEDULE = 'RUN EVERY HOUR' AS SELECT CURRENT_TIMESTAMP();

Solution

1. Step 1: Identify correct cron syntax for hourly schedule

   The cron expression '0 * * * * UTC' means at minute 0 of every hour in UTC time.

2. Step 2: Check Snowflake task syntax

   Snowflake requires SCHEDULE = 'USING CRON ...' format, so CREATE TASK my_task WAREHOUSE = my_wh SCHEDULE = 'USING CRON 0 * * * * UTC' AS SELECT CURRENT_TIMESTAMP(); matches this correctly.

3. Final Answer:

   CREATE TASK my_task WAREHOUSE = my_wh SCHEDULE = 'USING CRON 0 * * * * UTC' AS SELECT CURRENT_TIMESTAMP(); -> Option A

4. Quick Check:

   Use 'USING CRON' with correct cron string [OK]

Hint: Use 'USING CRON' with proper cron syntax for schedules [OK]

Common Mistakes:

• Omitting 'USING CRON' keyword
• Using invalid cron expressions
• Trying unsupported schedule keywords

3. Given the following task creation:

CREATE TASK daily_task WAREHOUSE = wh1 SCHEDULE = 'USING CRON 0 0 * * * UTC' AS INSERT INTO logs VALUES (CURRENT_TIMESTAMP());

What happens if you do NOT run ALTER TASK daily_task RESUME; after creation?

medium

A. The task runs immediately once and then stops

B. The task runs only when manually triggered

C. The task runs continuously without stopping

D. The task will not run automatically until resumed

Solution

1. Step 1: Understand task state after creation

   By default, a newly created task is in a suspended state and does not run automatically.

2. Step 2: Effect of not resuming the task

   Without running ALTER TASK ... RESUME, the task stays suspended and will not execute on schedule.

3. Final Answer:

   The task will not run automatically until resumed -> Option D

4. Quick Check:

   New tasks are suspended until resumed [OK]

Hint: Always resume tasks after creation to enable scheduling [OK]

Common Mistakes:

• Assuming tasks run immediately after creation
• Thinking tasks run continuously without control
• Believing tasks run only manually by default

4. You wrote this task creation statement:

CREATE TASK my_task WAREHOUSE = wh1 SCHEDULE = 'USING CRON 60 * * * * UTC' AS SELECT 1;

When you try to resume the task, it fails. What is the problem?

medium

A. The warehouse name is missing

B. The cron expression has an invalid minute value

C. The SQL statement is invalid

D. The task name is not allowed

Solution

1. Step 1: Check the cron expression

   Cron minute values must be between 0 and 59. '60' is invalid.

2. Step 2: Validate other parts

   Warehouse is specified, SQL is valid, and task name is allowed, so no issues there.

3. Final Answer:

   The cron expression has an invalid minute value -> Option B

4. Quick Check:

   Cron minutes must be 0-59 [OK]

Hint: Cron minutes must be 0-59, not 60 [OK]

Common Mistakes:

• Using 60 as a minute in cron
• Ignoring cron syntax errors
• Assuming warehouse or SQL errors cause failure

5. You want to create a task that runs a cleanup SQL every day at 3:30 AM UTC and uses warehouse 'clean_wh'. Which of the following is the correct way to create and enable this task?

hard

A. CREATE TASK cleanup_task WAREHOUSE = clean_wh SCHEDULE = 'USING CRON 30 3 * * * UTC' AS DELETE FROM temp_table; ALTER TASK cleanup_task RESUME;

B. CREATE TASK cleanup_task WAREHOUSE = clean_wh SCHEDULE = 'EVERY DAY AT 3:30' AS DELETE FROM temp_table; ALTER TASK cleanup_task RESUME;

C. CREATE TASK cleanup_task WAREHOUSE = clean_wh SCHEDULE = 'USING CRON 3 30 * * * UTC' AS DELETE FROM temp_table; ALTER TASK cleanup_task RESUME;

D. CREATE TASK cleanup_task WAREHOUSE = clean_wh SCHEDULE = 'USING CRON 30 3 * * *' AS DELETE FROM temp_table;

Solution

1. Step 1: Verify cron expression for 3:30 AM UTC

   The correct cron is '30 3 * * * UTC' meaning minute 30, hour 3.

2. Step 2: Check task creation and enabling

   Task must be created with warehouse, schedule, SQL, and then resumed with ALTER TASK ... RESUME.

3. Step 3: Compare options

   CREATE TASK cleanup_task WAREHOUSE = clean_wh SCHEDULE = 'USING CRON 30 3 * * * UTC' AS DELETE FROM temp_table; ALTER TASK cleanup_task RESUME; uses correct cron, warehouse, SQL, and resumes the task. CREATE TASK cleanup_task WAREHOUSE = clean_wh SCHEDULE = 'EVERY DAY AT 3:30' AS DELETE FROM temp_table; ALTER TASK cleanup_task RESUME; uses invalid schedule syntax. CREATE TASK cleanup_task WAREHOUSE = clean_wh SCHEDULE = 'USING CRON 3 30 * * * UTC' AS DELETE FROM temp_table; ALTER TASK cleanup_task RESUME; swaps hour and minute. CREATE TASK cleanup_task WAREHOUSE = clean_wh SCHEDULE = 'USING CRON 30 3 * * *' AS DELETE FROM temp_table; misses RESUME command.

4. Final Answer:

   CREATE TASK cleanup_task WAREHOUSE = clean_wh SCHEDULE = 'USING CRON 30 3 * * * UTC' AS DELETE FROM temp_table; ALTER TASK cleanup_task RESUME; -> Option A

5. Quick Check:

   Correct cron + resume task = CREATE TASK cleanup_task WAREHOUSE = clean_wh SCHEDULE = 'USING CRON 30 3 * * * UTC' AS DELETE FROM temp_table; ALTER TASK cleanup_task RESUME; [OK]

Hint: Use correct cron and always resume task after creation [OK]

Common Mistakes:

• Swapping hour and minute in cron
• Forgetting to resume the task
• Using unsupported schedule syntax