Zero-copy cloning in Snowflake - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is zero-copy cloning in Snowflake?

Zero-copy cloning is a way to create a copy of a database, schema, or table instantly without duplicating the actual data. It saves storage and time by sharing the original data until changes are made.

beginner

How does zero-copy cloning save storage space?

It saves space by not copying the data itself. Instead, the clone points to the original data. Only changes made after cloning use extra storage.

beginner

Can you modify data in a zero-copy clone without affecting the original?

Yes. Changes in the clone are stored separately. The original data remains unchanged, allowing safe experimentation or testing.

intermediate

Which Snowflake objects support zero-copy cloning?

Databases, schemas, and tables can be cloned using zero-copy cloning in Snowflake.

intermediate

What happens to storage costs when you create a zero-copy clone?

Initially, storage costs do not increase because no data is copied. Costs increase only when changes are made to the clone, using additional storage.

What does zero-copy cloning in Snowflake do?

A Creates a full physical copy of data instantly

B Deletes original data after cloning

C Copies data to an external storage

D Creates a copy without duplicating data until changes occur

Zero-copy cloning creates a copy that shares the original data until changes are made, saving storage.

Which Snowflake objects can you clone using zero-copy cloning?

A Only tables

B Only databases

C Databases, schemas, and tables

D Only schemas

Snowflake supports zero-copy cloning for databases, schemas, and tables.

What happens to the original data when you modify a zero-copy clone?

A Original data remains unchanged

B Original data is overwritten

C Original data is deleted

D Original data is moved to the clone

Changes in the clone do not affect the original data.

When do storage costs increase for a zero-copy clone?

A Immediately after cloning

B Only when changes are made to the clone

C When the clone is deleted

D Storage costs never increase

Storage costs increase only when the clone diverges by changes.

Why is zero-copy cloning faster than traditional copying?

A Because it skips copying data and shares existing data

B Because it copies data to a faster disk

C Because it compresses data during copy

D Because it deletes old data first

Zero-copy cloning is fast because it does not physically copy data initially.

Explain zero-copy cloning in Snowflake and how it benefits storage and performance.

Think about how sharing data instead of copying saves space and time.

Describe what happens to data and storage costs when you modify a zero-copy clone.

Consider how changes affect storage after cloning.

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