Incremental Data Matching Jobs
If you want to perform data matching for some number of nonexclusive subsets of the records in a business component, such as all the records that have been created or updated since you last ran data matching, use a WHERE clause that includes an appropriate timestamp, and also adjust the DqSetting clause of the command as shown in the following table.
| DqSetting Parameter Sequence | Valid Values | Comments |
|---|---|---|
First section |
Leave blank |
Specify as two adjacent quotation marks. |
Second section (Enforce Search Spec on Candidate Records) |
Yes or No (default) |
Specifies whether or not the same search specification is used for both the records whose duplicates are of interest and the candidate records that can include those duplicates. Use Yes for full data matching batch jobs. Use No for incremental data matching batch jobs. |
Third section |
Leave blank |
None. |
This kind of job is considered an incremental data matching job because data matching was done earlier and does not have to be redone at this time. In an incremental data matching batch job, the records for which you want to locate duplicates are defined by the search specification, but the candidate records that can include those duplicates can be drawn from the whole applicable database table. Incremental data matching batch jobs are useful if you run them regularly, such as once a week. A typical example of a command for an incremental data matching job is as follows:
run task for comp DQMgr with DqSetting="'','No',''",
bcname=Account, bobjname=Account, opType=DeDuplication, objwhereclause="[Updated] >
'08/18/2005 20:00:00'