In this blog post, I will show you what you need to pay special attention to when switching from Teradata to Snowflake.
We will analyze the impact of running DML statements (e.g., UPDATE or DELETE) in Snowflake and contrast it with Teradata’s Row Storage and Column Storage.
What happens when Teradata Rows are deleted from a table that is not Column-Partitioned?
Deletion and space reclamation in Teradata column-partitioned tables depend on format, operation and deployment. Do not generalize this historical container description to every current table; verify supported cleanup behavior for the actual storage.
What happens when Teradata Rows are deleted from a table that is Column-Partitioned?
Deletion and space reclamation in Teradata column-partitioned tables depend on format, operation and deployment. Do not generalize this historical container description to every current table; verify supported cleanup behavior for the actual storage.
What happens when data is deleted or modified in Snowflake?
Standard Snowflake tables use immutable columnar micro-partitions, generally 50–500 MB uncompressed. INSERT can create new partitions without rewriting an existing one; UPDATE/DELETE can create replacement data. Historical versions are retained under documented Time Travel/Fail-safe rules. Snowflake runs on multiple clouds, not only Amazon S3.
How can the performance of both systems be assessed?
I am currently missing more details about the implementation in Snowflake, but I will stay on it and update you as soon as I know more!
SQL compatibility is one part of a production migration. Explore our Teradata-to-Snowflake migration services for pipeline conversion, source-to-target reconciliation, and cutover planning.
Get the complete Teradata tuning book, free
Teradata Query Performance Tuning: The DWHPro Guide
By Roland Wenzlofsky & Artemios Vogiatzis
206 pages on statistics and demographics, access paths and indexes, query execution plans, and joins. Get the full PDF and practical Teradata updates from DWHPro.
Confirm your email to receive your download link. Privacy policy. Unsubscribe in any newsletter.
About the free bookPlanning a Teradata-to-Snowflake migration?
Review the assessment, conversion, reconciliation and cutover work needed for a controlled transition.
Get the complete Teradata tuning book, free
Teradata Query Performance Tuning: The DWHPro Guide
By Roland Wenzlofsky & Artemios Vogiatzis
206 pages on statistics and demographics, access paths and indexes, query execution plans, and joins. Get the full PDF and practical Teradata updates from DWHPro.
Confirm your email to receive your download link. Privacy policy. Unsubscribe in any newsletter.
About the free book
When an update is performed in Snowflake, the file belonging to this row is copied to a new one with the changes. Now you have 2 files. In the FoundationDB database, each table has a list of current files that belong to that table. During this update operation, the database is repointed to the new file. When a select operation is executed, this FoundationDB is checked for a current list of files, once that is retreived, the statistics on each file are applied to the query and only the files needed are read. Hope this helps.
Thank you very much for the explanation. Do you know maybe how joins are physically done in Snowflake? In Teradata, we can get information about all join methods, but I can’t find anything about Snowflake…