topic Re: Materialized Views Compute in Data Engineering

Materialized Views Compute

NikosLoutas — Wed, 09 Apr 2025 09:26:31 GMT

When creating a Materialized View (MV) without a schedule, there seems to be a cost associated with the MV once it is created, even if it is not queried.

The question is, once the MV is created, is there already a "hot" compute ready for use in case ad-hoc refreshes of the MV occur?

Re: Materialized Views Compute

Louis_Frolio — Wed, 09 Apr 2025 16:40:48 GMT

When a Materialized View (MV) is created in Databricks without a refresh schedule, there is no “hot” compute automatically kept ready for ad-hoc refreshes. However, the MV incurs costs associated with storage (vendor cost) because it physically stores precomputed query results in a table-like structure. In short, a materialized view is a table that incurrs cost when it is created or modified. However, once it is sitting in place (cloud storage) there are no Databricks charges, unless of course you are modifying it or accessing it via Spark (reads, optimizations, etc). Hope this helps. Lou.

Re: Materialized Views Compute

NikosLoutas — Thu, 10 Apr 2025 11:09:56 GMT

Thanks for the clarification, much appreciated !

Re: Materialized Views Compute

Louis_Frolio — Thu, 10 Apr 2025 14:14:41 GMT

Please select "Accept as Solution" so that others can benefit from this exchange. Regards, Louis.