Hi @IM_01,

Yes, Databricks MVs can do more than just row‑based and append‑only incremental refresh. 😊

PARTITION_OVERWRITE is still incremental in the sense that... Enzyme figures out which partitions changed since the last refresh... rebuilds just those partitions and overwrites them in the MV, and unchanged partitions are left as‑is, so you avoid a full recompute of the entire MV.

You can see which technique was used for a given refresh via the event log. If you see ... executed as PARTITION_OVERWRITE, that’s the partition‑level incremental path in action.

If this answer resolves your question, could you mark it as “Accept as Solution”? That helps other users quickly find the correct fix.