DWHPro Insights

Zero-Copy Clones: A Space and Time-Saving Solution for Database Management with Snowflake

By Roland Wenzlofsky ·

Zero-Copy Clones: A Space and Time-Saving Solution for Database Management with Snowflake

What Are Zero-Copy Clones?

We are all familiar with creating table backups before performing specific operations.

This is not a significant problem for smaller tables, as duplicates can be swiftly created and any errors can be rectified by reverting to the backup table.

If the table is enormous, making a copy can take a long time.
In addition, the required space is doubled. Especially at the go-live of new applications, this usually means an enormous expenditure of time and space.

A physical CREATE TABLE AS copy on the Teradata deployment discussed here consumes storage for its copied data. Assess current platform-specific clone, snapshot and recovery features separately rather than treating this historical example as a limit of all Teradata deployments.

Let’s explore more effective database systems. For instance, consider Snowflake, which successfully resolves these issues.

What is the basis for zero-copy clones in Snowflake?

Snowflake zero-copy cloning initially shares immutable micro-partitions through metadata. Snowflake supports multiple cloud platforms; this mechanism is not exclusively about Amazon S3. Retained history and later independent changes can incur storage costs.

How do zero-copy clones work in Snowflake?

A zero-copy clone initially references the source table’s existing immutable micro-partitions through metadata. The mechanism is not specific to Amazon S3. Initial data sharing avoids a full physical copy, while metadata, retained history and later independent changes can incur storage costs.

Changes made after cloning are independent: later source changes are not automatically reflected in the clone, and changed data can require new micro-partitions.

Snowflake syntax:
CREATE TABLE CustomerCopy CLONE Customer;

What is the advantage of zero-copy clones over the traditional method of copying tables?

Clone creation shares existing storage through metadata and does not require a warehouse scan. The unsupported one-terabyte/seven-minute claim has been removed. A clone is not forever storage-free: changes and retention can add costs. Compare current platform capabilities rather than asserting Teradata impossibility.

Is zero-copy cloning a replacement for a database backup?

Cloning is no replacement for a disaster recovery solution with a backup that is stored redundantly.

As demonstrated, creating zero-copy clones — also known as shallow copies of tables — simplifies many processes.

This historical comparison does not establish that zero-copy or snapshot facilities are absent from every other MPP system. Product capabilities and storage architectures change over time.

Do not infer current cloning capability from a simplified account of cylinder and master indexes. Consult the supported features and recovery semantics of the particular Teradata deployment.

Are there any other MPP systems that support zero-copy cloning besides Snowflake? If so, please share by leaving a comment below.

Planning a Teradata-to-Snowflake migration?

Review the assessment, conversion, reconciliation and cutover work needed for a controlled transition.

Explore migration services

Practical data engineering insights, regularly

Join more than 3,500 data professionals: a regular newsletter with practical insights on data engineering, new data platforms (Snowflake, Databricks, Teradata) and AI.

Follow DWHPro in Google to see our articles more often in Search.

Leave a Comment

Get more practical Snowflake advice

Join the DWHPro newsletter for Snowflake performance tips, cost optimization ideas and data warehousing insights.

Protected by Security by CleanTalk and CleanTalk Anti-Spam