Micro-partitions are shared at the beginning, once changes are made to the copied table, the underlaying data changes and the tables may not share the same micro-partitions.
Though it is true that once a table is cloned it inherits time-travel, clustering keys, comments, ... So I think it's B
- Snowflake’s zero-copy cloning feature provides a convenient way to quickly take a “snapshot” of any table, schema, or database and create a derived copy of that object which initially shares the underlying storage. This can be extremely useful for creating instant backups that do not incur any additional costs (until changes are made to the cloned object).
- owever, cloning makes calculating total storage usage more complex because each clone has its own separate life-cycle. This means that changes can be made to the original object or the clone independently of each other and these changes are protected through CDP.
https://docs.snowflake.com/en/user-guide/tables-storage-considerations.html#cloning-tables-schemas-and-databases
A voting comment increases the vote count for the chosen answer by one.
Upvoting a comment with a selected answer will also increase the vote count towards that answer by one.
So if you see a comment that you already agree with, you can upvote it instead of posting a new comment.
yaho5
9 months, 1 week agoHarpreetwal
1 year, 8 months agoMultiCloudIronMan
1 year, 8 months agoBigDataBB
1 year, 11 months agosakis213
1 year, 11 months agosakis213
2 years agosakis213
1 year, 12 months ago