If a table is cloned, historical data for the table clone begins at the time/point when the clone was created.

Master the SnowPro Advanced Architect Test with flashcards, multiple-choice questions, and detailed explanations. Prepare thoroughly for your certification!

Multiple Choice

If a table is cloned, historical data for the table clone begins at the time/point when the clone was created.

Explanation:
When you clone a table in Snowflake, you create a new object that references the source data as it exists at the exact moment of cloning. The clone is effectively a snapshot at that creation time, and after that moment any changes to the source do not alter the clone. Time Travel works per object, so you can query the clone as it existed at or after its creation, up to its retention period. There is no historical data for the clone from before it was created because the clone did not exist then. Thus, the clone’s historical data begins at the moment of its creation, and you can travel forward in time from there (subject to the clone’s own retention).

When you clone a table in Snowflake, you create a new object that references the source data as it exists at the exact moment of cloning. The clone is effectively a snapshot at that creation time, and after that moment any changes to the source do not alter the clone. Time Travel works per object, so you can query the clone as it existed at or after its creation, up to its retention period. There is no historical data for the clone from before it was created because the clone did not exist then. Thus, the clone’s historical data begins at the moment of its creation, and you can travel forward in time from there (subject to the clone’s own retention).

Subscribe

Get the latest from Passetra

You can unsubscribe at any time. Read our privacy policy