Zero-copy cloning is a feature that allows creating a clone of a table, schema, or database without

physically copying the data. Zero-copy cloning is suitable for scenarios where the cloned object needs

to have the same data and metadata as the original object, and where the cloned object does not

need to be modified or updated frequently. Zero-copy cloning is also suitable for scenarios where the

cloned object needs to be shared within the same Snowflake account or across different accounts in

the same cloud region2

However, zero-copy cloning is not suitable for scenarios where the cloned object needs to have

different data or metadata than the original object, or where the cloned object needs to be modified

or updated frequently. Zero-copy cloning is also not suitable for scenarios where the cloned object

needs to be shared across different accounts in different cloud regions. In these scenarios, copying of

data would be required, either by using the COPY INTO command or by using data sharing with

secure views3

The following are examples of development and testing scenarios where copying of data would be

required, and zero-copy cloning would not be suitable:

Developers create their own datasets to work against transformed versions of the live data. This

scenario requires copying of data because the developers need to modify the data or metadata of

the cloned object to perform transformations, such as adding, deleting, or updating columns, rows,

or values. Zero-copy cloning would not be suitable because it would create a read-only clone that

shares the same data and metadata as the original object, and any changes made to the clone would

affect the original object as well4

Data is in a production Snowflake account that needs to be provided to Developers in a separate

development/testing Snowflake account in the same cloud region. This scenario requires copying of

data because the data needs to be shared across different accounts in the same cloud region. Zero-

copy cloning would not be suitable because it would create a clone within the same account as the

original object, and it would not allow sharing the clone with another account. To share data across

different accounts in the same cloud region, data sharing with secure views or COPY INTO command

can be used5

The following are examples of development and testing scenarios where zero-copy cloning would be

suitable, and copying of data would not be required:

Production and development run in different databases in the same account, and Developers need to

see production-like data but with specific columns masked. This scenario can use zero-copy cloning

because the data needs to be shared within the same account, and the cloned object does not need

to have different data or metadata than the original object. Zero-copy cloning can create a clone of

the production database in the development database, and the clone can have the same data and

metadata as the original database. To mask specific columns, secure views can be created on top of

the clone, and the developers can access the secure views instead of the clone directly6

Developers create their own copies of a standard test database previously created for them in the

development account, for their initial development and unit testing. This scenario can use zero-copy

cloning because the data needs to be shared within the same account, and the cloned object does

not need to have different data or metadata than the original object. Zero-copy cloning can create a

clone of the standard test database for each developer, and the clone can have the same data and

metadata as the original database. The developers can use the clone for their initial development

and unit testing, and any changes made to the clone would not affect the original database or other

clones7

The release process requires pre-production testing of changes with data of production scale and

complexity. For security reasons, pre-production also runs in the production account. This scenario

can use zero-copy cloning because the data needs to be shared within the same account, and the

cloned object does not need to have different data or metadata than the original object. Zero-copy

cloning can create a clone of the production database in the pre-production database, and the clone

can have the same data and metadata as the original database. The pre-production testing can use

the clone to test the changes with data of production scale and complexity, and any changes made to

the clone would not affect the original database or the production environment8 Reference:

1: SnowPro Advanced: Architect | Study Guide 9

2: Snowflake Documentation | Cloning Overview

3: Snowflake Documentation | Loading Data Using COPY into a Table

4: Snowflake Documentation | Transforming Data During a Load

5: Snowflake Documentation | Data Sharing Overview

6: Snowflake Documentation | Secure Views

7: Snowflake Documentation | Cloning Databases, Schemas, and Tables

8: Snowflake Documentation | Cloning for Testing and Development

: SnowPro Advanced: Architect | Study Guide

: Cloning Overview

: Loading Data Using COPY into a Table

: Transforming Data During a Load

: Data Sharing Overview

: Secure Views

: Cloning Databases, Schemas, and Tables

: Cloning for Testing and Development