When working with dimension tables that change frequently, what is the recommended way to manage costs?
When working with dimension tables that change frequently, what is the recommended way to manage costs?
Dimension tables often store relatively small amounts of data but can change frequently due to updates, inserts, or deletes. Managing costs efficiently involves minimizing storage costs associated with Time Travel and Fail-safe while maintaining the necessary data history for recovery purposes.
https://docs.snowflake.com/en/user-guide/dynamic-tables-best-practices#label-best-practices-create-transient-dts "Use transient dynamic tables to reduce storage cost Transient dynamic tables maintain data reliably over time and support Time Travel within the data retention period, but don’t retain data beyond the fail-safe period. By default, dynamic table data is retained for 7 days in fail-safe storage. For dynamic tables with high refresh throughput, this can significantly increase storage consumption. Therefore, you should make a dynamic table transient only if its data doesn’t need the same level of data protection and recovery provided by permanent tables." I would say A
Please, disregard my previous comment. I addressed it as for dynamic tables, which is a mistake. On the other hand, in variant A , it is about a 7 day Time Travel period which cannot be kept, as it is not by default value. In addition, C is not right, because cloning transient table to permanent table cannot be cloned into permanent tables. I am not sure about the answer, I need to search more.