KEMBAR78
Snowflake Best Practices | PDF
Scribd
Upload
217 views7 pages

Snowflake Best Practices

The document discusses best practices for using Snowflake including using transient tables for staging, permanent tables for production, proper data types when creating tables, running updates on staging before pushing to production, and development databases being transient. It also discusses clone best practices, ETL load methods, using large clusters for copy commands, and setting retention periods.

Uploaded by

mysites220
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
217 views7 pages

Snowflake Best Practices

The document discusses best practices for using Snowflake including using transient tables for staging, permanent tables for production, proper data types when creating tables, running updates on staging before pushing to production, and development databases being transient. It also discusses clone best practices, ETL load methods, using large clusters for copy commands, and setting retention periods.

Uploaded by

mysites220
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 7

Snowflake important

features
• CLONE
• TRANSIENT, TEMPORARY , PERMANENT
TABLES.
• FAIL SAFE.
• TIME TRAVEL.
• RETENTION PERIOD.
• COPY COMMAND.
• INTERNAL STAGE , EXTERNAL STAGE.
• SAMPLING.
Best practices on
tables
• All staging tabels should be transient.

• All production tables should be permanent.

• While creating tables give proper datatypes.

• Always run updates on staging tables before pushing data to


prod tables.

• Development database should be transient.


ETL load convectional method
Clone best practice
Other use cases
Best practice using
virtual warehouse
• > Development team should use same virtual clusters while
doing development.

• > For a development cluster set auto shut down to max period.

• > While loading data to a table sort by keys on which you want
to query data in future.

• > Use large cluster to run copy command. Run copy command
on smaller chunks of files.

• > While executing queries always use column names instead of


using `*`. If you want to use `*` use limit clause along with it.
Best practice retention
period and time travell

• Set retention period of stage tables to 0.

• For production tables set retention period


to max.

• Set retention period to 0 for cloned


database for analytics.

You might also like