https://community.databricks.com/t5/data-engineering/how-to-disable-full-refresh-on-materialized-view-if-the-src-is/m-p/152209#M53787 <P>Hi,</P><P>Is there any option to control refresh rate of materialized view such as , even the dlt is triggered in full refresh mode and src Streaming tables are not updated then the full refresh should not happen on mvs . Is there any way to achieve this.</P> Thu, 26 Mar 2026 17:40:22 GMT IM_01 2026-03-26T17:40:22Z https://community.databricks.com/t5/data-engineering/how-to-disable-full-refresh-on-materialized-view-if-the-src-is/m-p/152209#M53787 <P>Hi,</P><P>Is there any option to control refresh rate of materialized view such as , even the dlt is triggered in full refresh mode and src Streaming tables are not updated then the full refresh should not happen on mvs . Is there any way to achieve this.</P> Thu, 26 Mar 2026 17:40:22 GMT https://community.databricks.com/t5/data-engineering/how-to-disable-full-refresh-on-materialized-view-if-the-src-is/m-p/152209#M53787 IM_01 2026-03-26T17:40:22Z https://community.databricks.com/t5/data-engineering/how-to-disable-full-refresh-on-materialized-view-if-the-src-is/m-p/152282#M53802 <P>Hi,</P> <P>The only way that I think you can do this is to seperate out the Materialized views from the pipelines into standalone SQL jobs with a TRIGGER ON UPDATE clause. This means they only run if the streaming tables are updated. However, this approach is fine if you just have a few MVs but if there are lots and there are many interdependencies it won't be good to manage. I think the thing to consider is that MVs only process incremental records so if the records in the source tables are changed the MV process kicks in but it will barely use any compute as it won't be doing anything.</P> <P>I hope this helps.<BR /><BR />Thanks,<BR /><BR />Emma</P> Fri, 27 Mar 2026 09:57:40 GMT https://community.databricks.com/t5/data-engineering/how-to-disable-full-refresh-on-materialized-view-if-the-src-is/m-p/152282#M53802 emma_s 2026-03-27T09:57:40Z