DATABASES Signal 510
Binlog CDC for MySQL to BigQuery captures deletes and intermediate updates that periodic syncs miss
↗
Binlog-based Change Data Capture for MySQL captures every change, including deletes and intermediate updates, unlike periodic SELECT-based syncs, but requires specific binlog settings to work reliably.
Periodic syncs silently miss deletes and intermediate row states, so downstream BigQuery tables can be incomplete without anyone noticing. Binlog CDC guarantees a complete change history, but only if MySQL is configured with ROW-based logging and FULL row images, and if binlog retention covers downtime.
Written by elseif from the cluster below · every claim links back to a sourceThe three things worth knowing
Periodic SELECT-based syncs only see the current state, missing deletes and intermediate updates.
Binlog CDC reads every change from MySQL's binary log in order, capturing complete row states.
CDC requires binlog_row_image=FULL, no PARTIAL_JSON, proper replication privileges, a unique server-id, and sufficient binlog retention.
THE CLUSTER