I would like to add few things in addition to Delta handling covered by Ian Daniel in his blog. The Delta option is used more often in a “To Pass” rather than in a “From Pass”. It is a very powerful feature which helps to reduce the load on the network and target systems. While enabling the delta, a delta table name is provided. During its first run, this table stores all the entries in hashed format. In subsequent runs, the system compares the hash value of the new record with the hash value stored in delta table. If it is different or missing, it writes the entry and stores the hash value in delta table. If its the same, it marks the record as processed in the delta table and does not write any thing to the target.
An LDAP is most often used to load users into IdM system. In such cases, a Delta could be enabled to avoid reading all the users everyday. A field to pay more attention is the “Max limit for mark for deletion” and “Max real updates”. The former value has to be provided based on the average number of users deleted/terminated from your organization. Make sure you set that to a very reasonable value based on your organization. The last thing you will want to see is all users in the target system being deleted just because of some corrupt data passed into IdM from a source system (Single Point Of Failure). If you set the value to say 3%, and if the number of records being deleted exceeds this value, nothing will be marked for deletion in the Delta table and no records would be deleted.