---
title: "REFRESH MATERIALIZED VIEW"
sidebarTitle: "REFRESH MATERIALIZED VIEW"
description: "Bringing a materialized view's stored result up to date."
icon: arrows-rotate
keywords: ["refresh materialized view", "cascade"]
availability:
  embedded: unavailable
  enterprise: available
---

A LanceDB extension with no DataFusion equivalent.

<CodeGroup>
```sql SQL icon="database"
REFRESH MATERIALIZED VIEW <name>
  [WITH (full = <boolean>)]
```
</CodeGroup>

<CodeGroup>
```sql SQL icon="database"
REFRESH MATERIALIZED VIEW chunks
REFRESH MATERIALIZED VIEW chunks WITH (full = true)
```
</CodeGroup>

A refresh updates the view's stored result. Refresh views in dependency order,
starting with their source views. `full = true` forces a complete rebuild
even when the sources are unchanged; the default, `false`, refreshes
incrementally when supported and rebuilds otherwise.

<Note>
`CASCADE` is not accepted by the SQL implementation described here,
regardless of what a local SDK's `refresh()` method accepts -- do not
assume the two option sets match.
</Note>

## Watching a refresh {#watching}

A refresh submits work that outlives the call. Track it with
[`SHOW JOBS`](/sql/ddl/job#show), and diagnose failures with
[`SHOW ERRORS`](/sql/ddl/job#errors). For per-split progress, worker fleet
detail, and a `DESCRIBE JOB` example, see [Watching a refresh](/sql/dml/refresh#watching).

## See also {#see-also}

<CardGroup cols={2}>
  <Card title="Materialized View" icon="table" href="/sql/ddl/materialized-view">
    Creating the view this refreshes.
  </Card>
  <Card title="Refresh a materialized view" icon="layer-group" href="/feature-engineering/refresh-materialized-view">
    The same operation from the SDKs, and automatic refresh.
  </Card>
  <Card title="REFRESH COLUMN" icon="arrows-rotate" href="/sql/dml/refresh-column">
    Filling a computed column, instead of a view.
  </Card>
</CardGroup>