Understanding the costs of dynamic tables¶
Dynamic tables incur cost in three ways:
Storage: Dynamic tables require storage as other tables do. Storage cost is based on a flat rate per terabyte (TB).
Cloud services compute: Dynamic tables use cloud services compute to trigger refreshes when an underlying base object has changed. Cloud services compute cost is subject to the constraint that Snowflake only bills if the daily cloud services cost is greater than 10% of the daily warehouse cost for the account.
Virtual warehouse compute: Dynamic tables require a virtual warehouse to run the queries against base objects when they are initially populated and later when they are continuously refreshed. As data in the underlying base objects changes, changes are applied to the associated dynamic tables. Snowflake bills your account credits based on virtual warehouse usage as a result of these operations.
While in preview, dynamic tables are part of Standard Edition, and no additional charges (apart from the storage and compute) are incurred.
Dynamic tables require a virtual warehouse to perform updates. Snowflake recommends testing dynamic tables using dedicated warehouses in order to understand related costs.
Dynamic tables use cloud services compute to determine whether changes occurred to base objects since the last refresh. If no changes are detected, no virtual warehouse credits are consumed (because there is no data to refresh); but cloud services compute is still used for maintenance and periodic checks. Additionally, if the associated virtual warehouse is suspended and no changes are detected, the warehouse is NOT resumed. Conversely, if changes are detected, the virtual warehouse is resumed to process the updates. For general information on cost, see Understanding overall cost.