Setting an earliest data inclusion date and backfilling data
When you replicate data, you may encounter two situations that impact the performance and usefulness of the replication. First, you may not want to include data from the earliest time that data exists in the business class. For example, for your business's analytical needs, you may want only data going back six months whereas the business class contains data going back several years. Second, when business classes have a large amount of data, the initial replication of that data can be resource and time intensive. To address these situations, data replications includes two features.
- First, to avoid replicating data from earlier time periods, you can set an "earliest change date to include". Replication then includes only data that has been created or modified on or after that date.
- Second, to avoid long-running replication processes, you can perform the initial replication using an "earliest change date to include" value, and then use the Backfill data action to incrementally replicate data for earlier time periods than the "earliest change date to include" value.
See the following steps for details on how to use the Earliest change date to include field and the Backfill data action. This example assumes that you want to use both the Earliest change date to include field and the Backfill data action.