Zero-copy cloning in Snowflake - Commands & Configuration

Introduction

Zero-copy cloning lets you make a copy of a database or table instantly without using extra storage. It solves the problem of waiting and paying for full copies by sharing the original data behind the scenes.

When you want to test changes on a database without affecting the original data.

When you need a quick backup of a table for analysis without extra storage costs.

When you want to create multiple environments (dev, test) from the same data instantly.

When you want to save storage by avoiding full data duplication.

When you want to experiment with data transformations safely.

Commands

This command creates a new database called 'mydb_clone' as a zero-copy clone of the existing 'mydb'. It instantly copies the structure and data without extra storage.

Terminal

CREATE DATABASE mydb_clone CLONE mydb;

Expected Output

Database MYDB_CLONE successfully created.

This command verifies that the cloned database 'mydb_clone' exists and is ready to use.

Terminal

SHOW DATABASES LIKE 'mydb_clone';

Expected Output

name       | created_on          | owner

MYDB_CLONE | 2024-06-01 12:00:00 | USER_NAME

This command switches the session to use the cloned database so you can run queries or changes on it.

Terminal

USE DATABASE mydb_clone;

Expected Output

Database changed.

This command checks the number of rows in a table inside the cloned database to confirm data is accessible.

Terminal

SELECT COUNT(*) FROM mytable;

Expected Output

COUNT(*)

1000

Key Concept

If you remember nothing else from zero-copy cloning, remember: it creates instant copies without extra storage by sharing the original data behind the scenes.

Common Mistakes

Trying to clone a database that does not exist.

The clone command fails because there is no source database to copy from.

Make sure the source database exists before running the clone command.

Assuming changes in the clone affect the original database.

Clones are independent after creation; changes do not reflect back to the original.

Treat the clone as a separate database for changes and testing.

Expecting the clone to use the same storage as the original after many changes.

Over time, changes in the clone consume additional storage as data diverges.

Monitor storage usage if clones are heavily modified.

Summary

Use CREATE DATABASE ... CLONE to make an instant copy without extra storage.

Verify the clone exists with SHOW DATABASES and switch to it with USE DATABASE.

Query the clone like a normal database; changes do not affect the original.

Practice

1. What is the main benefit of zero-copy cloning in Snowflake?

easy

A. It deletes the original data after cloning.

B. It compresses data to save storage space.

C. It encrypts data automatically during cloning.

D. It creates instant copies without duplicating the original data.

Solution

1. Step 1: Understand zero-copy cloning concept

   Zero-copy cloning creates a copy of data instantly without physically duplicating the data.

2. Step 2: Identify the main benefit

   This saves storage and time because the clone shares the original data until changes are made.

3. Final Answer:

   It creates instant copies without duplicating the original data. -> Option D

4. Quick Check:

   Zero-copy cloning = instant copy without duplication [OK]

Hint: Zero-copy cloning shares data, no extra storage used [OK]

Common Mistakes:

• Thinking cloning duplicates all data immediately
• Confusing cloning with data encryption
• Assuming original data is deleted after cloning

2. Which of the following is the correct syntax to create a zero-copy clone of a table named sales_data in Snowflake?

easy

A. CREATE TABLE sales_data_clone AS CLONE sales_data;

B. CREATE CLONE sales_data_clone FROM sales_data;

C. CREATE TABLE sales_data_clone CLONE sales_data;

D. CLONE TABLE sales_data TO sales_data_clone;

Solution

1. Step 1: Recall Snowflake cloning syntax

   The correct syntax to clone a table is: CREATE TABLE new_table CLONE original_table;

2. Step 2: Match syntax with options

   CREATE TABLE sales_data_clone CLONE sales_data; matches the correct syntax exactly.

3. Final Answer:

   CREATE TABLE sales_data_clone CLONE sales_data; -> Option C

4. Quick Check:

   CREATE TABLE ... CLONE ... is correct syntax [OK]

Hint: Use CREATE TABLE new_table CLONE original_table [OK]

Common Mistakes:

• Using CREATE CLONE instead of CREATE TABLE ... CLONE
• Adding AS before CLONE incorrectly
• Using CLONE TABLE ... TO syntax which is invalid

3. Consider this Snowflake SQL snippet:

CREATE TABLE original (id INT, value STRING);
INSERT INTO original VALUES (1, 'A'), (2, 'B');
CREATE TABLE clone_table CLONE original;
INSERT INTO clone_table VALUES (3, 'C');
SELECT COUNT(*) FROM original;

What will be the output of the SELECT query?

medium

A. 2

B. Error

C. 0

D. 3

Solution

1. Step 1: Understand cloning and data insertion

   The clone_table is a zero-copy clone of original, sharing data initially. Inserting into clone_table does not affect original.

2. Step 2: Count rows in original table

   Original has 2 rows inserted initially and remains unchanged after clone_table insert.

3. Final Answer:

   2 -> Option A

4. Quick Check:

   Original rows unchanged after clone insert [OK]

Hint: Inserts to clone don't affect original table [OK]

Common Mistakes:

• Assuming insert in clone adds rows to original
• Thinking clone is a full independent copy immediately
• Expecting error due to cloning

4. You tried to create a zero-copy clone of a database using:

CREATE DATABASE clone_db CLONE original_db;

But received an error. What is the most likely cause?

medium

A. The original database does not exist.

B. You cannot clone a database, only tables.

C. The clone syntax requires the keyword TABLE.

D. You need to specify a schema when cloning a database.

Solution

1. Step 1: Check cloning rules for databases

   Snowflake supports cloning databases if the original database exists.

2. Step 2: Identify error cause

   If the original_db does not exist, cloning fails with an error.

3. Final Answer:

   The original database does not exist. -> Option A

4. Quick Check:

   Cloning requires existing source database [OK]

Hint: Ensure original database exists before cloning [OK]

Common Mistakes:

• Thinking databases cannot be cloned
• Adding TABLE keyword incorrectly
• Assuming schema must be specified

5. You want to create a zero-copy clone of a large table for testing, but only want to clone data as it was at a specific past time. Which Snowflake feature should you use with cloning?

hard

A. Use a full data export and import instead of cloning.

B. Use Time Travel to specify the past timestamp during cloning.

C. Clone the table and then manually delete unwanted rows.

D. Use a materialized view to clone the data at that time.

Solution

1. Step 1: Understand cloning with Time Travel

   Snowflake allows cloning data as it existed at a past time using Time Travel feature.

2. Step 2: Apply Time Travel in cloning

   You specify the timestamp or offset in the clone statement to get data snapshot at that time.

3. Final Answer:

   Use Time Travel to specify the past timestamp during cloning. -> Option B

4. Quick Check:

   Time Travel + cloning = snapshot at past time [OK]

Hint: Combine Time Travel with clone for past data snapshot [OK]

Common Mistakes:

• Thinking cloning alone can get past data
• Using export/import which is slower
• Using materialized views which don't clone data