--- title: "Refresh a materialized view" sidebarTitle: "Refresh Materialized View" description: "Bring a materialized view up to date after its source data changes." icon: arrows-rotate keywords: ["materialized view", "refresh", "auto_refresh_enabled", "auto_refresh_interval_seconds"] availability: embedded: unavailable enterprise: available --- Refresh a [materialized view](/feature-engineering/materialized-views) to bring its stored rows up to date after the source table changes. In SQL this is [`REFRESH MATERIALIZED VIEW`](/sql/dml/refresh-materialized-view). ## Refresh a view {#refresh} ```python Python icon="python" view.refresh() ``` In LanceDB Embedded, every refresh rebuilds the view completely from its source query -- there is no incremental refresh there. Calling it again with no source changes still rebuilds and commits a new table version. In LanceDB Enterprise, the server chooses the refresh mode instead; pass `full=True` to force a full rebuild there too. In LanceDB Embedded, the result reports what the refresh did: ```python Python icon="python" result = view.refresh() result.rows_written # rows in the rebuilt view result.source_version # the source table version the view now reflects result.version # the view's own new table version ``` LanceDB Enterprise refreshes run through its SQL job adapter, which doesn't expose these metrics: `mode`, `rows_written` and `source_version` are all `None` on an Enterprise result, even though the refresh itself ran. Pass `source_version=N` to refresh against a particular source version instead of the latest. This is a LanceDB Embedded capability only -- LanceDB Enterprise's SQL refresh does not support pinning a source version: ```python Python icon="python" view.refresh(source_version=12) # LanceDB Embedded only ``` Use `view.table.count_rows()` for the view's row count at any time; on LanceDB Embedded it always matches `rows_written` from the most recent refresh. ## Automatic refresh {#auto-refresh} A materialized view can refresh itself on a schedule instead of waiting for an explicit `refresh()` call. See [Auto Refresh](/enterprise/auto-refresh) for enabling it at creation, the SQL and SDK forms for changing the setting afterward, and how it differs from a computed column's per-output granularity. ## When a refresh fails {#failures} A refresh replaces the view's stored rows in one commit, so a failure leaves the view as it was after its last successful refresh. Fix the cause and refresh again. ## Related guides {#next} Define the query a view stores. The same idea, for a single derived column. Refresh on a schedule instead of calling this yourself.