Does Switching From CT/CDC to Binary Log Reader Trigger a Re-sync or Incur MAR?

Question

Does switching from the change tracking (CT) or change data capture (CDC) incremental sync methods to Binary Log Reader trigger a re-sync or contribute to monthly active rows (MAR)?

Environment

• Connector: SQL Server
• Incremental sync method: change tracking (CT) or change data capture (CDC)

Answer

Yes, switching from change tracking or change data capture to Binary Log Reader triggers a one-time historical re-sync of all selected tables. The re-sync refreshes the existing destination data without data loss and enables Fivetran to begin tracking changes through the transaction log.

During the re-sync, unchanged historical rows do not count toward paid MAR. Historical rows with changes contribute to MAR. After the re-sync, new or modified rows processed during incremental syncs count toward MAR as usual.

The re-sync can take about as long as an initial sync, so we recommend scheduling the change during a low-activity window when possible.

For more information, see our Binary Log Reader FAQs.