Skip to content
BENIBIX Learn

Change Data Capture vs Incremental Load

People think asking a table for rows with a newer time is CDC. That is an incremental load. It asks the table on a timer and only sees rows as they are now. CDC reads the database's change log, so it catches every change, deletes too, within seconds.

Data📥 Ingestion & Streaming

Change Data Capture (CDC)

It copies each change in a database right as it is made.

Change data capture copies each change in a database as it happens. It reads the database's own change log. Every insert, update and delete is written there. Each change becomes an event that is sent on to other systems. So a warehouse or a search index stays in step within seconds. The source database barely notices.

Example
A bank uses CDC on its accounts table. Each balance change reaches the fraud system in about two seconds.
Why it matters
It catches every update and every delete. A nightly copy misses those. It also puts little load on the app's database.
Full entry
Data📥 Ingestion & Streaming

Incremental Load

Copy only what is new since last time. Do not copy it all again.

An incremental load copies only the rows that are new or changed since the last run. It keeps a mark of how far it got, often the latest updated time or the highest ID. The next run asks only for rows past that mark. A full load copies the whole table each time instead. Incremental loads are far faster on big tables.

Example
The orders table has 50 million rows. Each hour, the job copies only the few thousand that changed.
Why it matters
Big tables cannot be copied in full every hour. An incremental load keeps the job small and fast.
Full entry

In one line

Change Data Capture (CDC)
It copies each change in a database right as it is made.
Incremental Load
Copy only what is new since last time. Do not copy it all again.