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.
