# Incremental Model (dbt)

> A dbt model that adds just the new rows on each run.

**Field:** Data Engineering  
**Category:** Processing  
**Also known as:** dbt Incremental Model, Incremental Materialization

## Think of it like

It is like a diary. Each day you add a page. You do not write the whole book again.

## Definition

An incremental model is a dbt model that adds only new or changed rows on each run. The first run builds the whole table. Later runs use the is_incremental() check to pick just the new rows and add them. This is much faster than rebuilding a big table every time. The --full-refresh flag rebuilds it from scratch.

## Example

An events table has 2 billion rows and gets 5 million a day. The incremental model adds the 5 million in minutes instead of rebuilding all of it.

## Example code

```sql
{{ config(materialized='incremental') }}

select * from {{ ref('events') }}
{% if is_incremental() %}
where event_time > (select max(event_time) from {{ this }})
{% endif %}
```

On later runs, only rows newer than the table's latest one are read.

## Why it matters

Big tables would take hours and cost a lot to rebuild each night. Adding only new rows keeps runs short and cheap.

## Common mistake

Forgetting late rows. A row that arrives late with an old time is skipped by the filter for good.

## Three principles

- **Build once.** The first run makes the full table.
- **Add the new.** Later runs pick only new rows.
- **Full refresh.** Rebuild from scratch when logic changes.

## Related terms

- [dbt (Data Build Tool)](https://learn.benibix.com/term/data/dbt)
- [dbt Model](https://learn.benibix.com/term/data/dbt-model)
- [Incremental Load](https://learn.benibix.com/term/data/incremental-load)
- [dbt Snapshot](https://learn.benibix.com/term/data/dbt-snapshot)
- [Late-Arriving Data](https://learn.benibix.com/term/data/late-arriving-data)

## Told apart from

- [dbt Snapshot vs Incremental Model](https://learn.benibix.com/compare/dbt-snapshot-vs-incremental-model): People think a dbt snapshot and an incremental model do the same job, since both add rows to a table over time. An incremental model adds new rows to save time, and a changed row can replace the old one. A snapshot is there to keep history. A changed row is added as a new version, and the old one stays. Use a snapshot when you need to know what a value used to be.

![A dbt project from left to right. A source, the raw table shop.orders loaded by other tools, feeds a model called stg_orders, a SELECT that cleans it. That feeds a highlighted incremental model called orders, where each run adds only the new rows. Under it, tests check that order_id is unique and not null, find 0 failing rows and pass. Under the source, a snapshot called orders_snapshot keeps each old version with valid from and to dates.](https://learn.benibix.com/diagrams/dat-dbt-project.svg)

---

Source: https://learn.benibix.com/term/data/incremental-model
Author: Behnia Zarei (a developer in Vienna, Austria, who builds and teaches data, AI and business intelligence at BENIBIX)
Publisher: BENIBIX Learn (https://learn.benibix.com/)
Last updated: 2026-11-19
Licence: CC BY 4.0 (https://creativecommons.org/licenses/by/4.0/). Quote freely with attribution.
