Why Do Salesforce History Tables Use So Much MAR?

You may notice that Salesforce history tables contribute significantly to your connection's Monthly Active Rows (MAR) usage. Find out why they generate so much MAR and how to reduce usage.

Why do history tables generate so much MAR?

History tables have many active rows due to the combination of how the history tables are structured and how we define an active row.

The purpose of the history tables is to capture every single change made to a particular record. When we sync that data, every change has a unique ID associated with it. We calculate an active row based on the primary key of any given table, and the ID column of the history table is the primary key.

With history tables, each change is a new row with a new unique ID. There's never an ID that gets updated which does not count as an additional active row.

How to reduce MAR usage

Instead of syncing the Salesforce history tables directly, enable Fivetran's history mode for the corresponding table that each history table tracks:

1. In Fivetran, go to your Salesforce connection page.
2. Select the Schema tab.
3. Deselect the checkbox next to the history table you want to exclude from your syncs.
4. Find the table that the history table tracks.
5. In the Sync mode column, click on the mode name to open a drop-down menu, then select History mode.
6. Repeat steps 3 to 5 for all history tables you want to exclude.
7. Click Save changes.