When you create a mapping, specify one of the following update modes:

A series of delta updates is called a delta queue. When you create a processing mapping and select delta update instead of full update, select one of the following delta update options:

If you do not want to do an initial full transfer of data, but want to extract only changed data, you can configure for delta initialization without transfer. For more information about configuring delta initialization without transfer, see the Informatica How-To Library article "How to Configure SAP BCI Delta Initialization Without Transfer":

https://docs.informatica.com/integration-cloud/cloud-data-integration-connectors/h2l/configuring-the-simba-mongodb-jdbc-driver-options-for-mongodb-co/abstract.html

When you create the processing mapping, based on your business needs, you can initialize more than one delta queue for each DataSource. Use multiple delta queues when you want to select data from a non-continuous range that cannot be defined in a single delta queue.

For example, to compare data from item numbers 1 through 4 to item numbers 11 through 14, you need to use two delta queues because the item numbers are not in one continuous range.

The following table shows two delta queues for two item ranges updated at the end of each quarter:

At the end of the first quarter, you initialize both delta queues and perform full updates, because there are no previous delta updates. At the end of the second, third, and fourth quarters, both delta queues extract only the data that has changed since the previous update.

When you create a processing mapping, you can create a new delta queue or edit an existing delta queue. For each new delta queue, you need to specify selection criteria.