Full Data Matching Jobs

In a full data matching job, the records for which you want to locate duplicates and the candidate records that can include those duplicates are defined by the same search specification. A full data matching job is specified with the value Yes in the DQSetting parameter, see the following table.

Full data matching jobs are useful when:

• You want to perform data matching on a whole database table.

• You are setting up the data quality installation.

• You perform data matching for the customer data for a particular business component for the first time.

A typical example of a command for a full data matching job is as follows:

run task for comp DQMgr with DqSetting="'','Yes','account_match.xml'", 
bcname=Account, bobjname=Account, opType=DeDuplication, objwhereclause="[Name] LIKE 
'A*'"

Jobs like this that perform data matching for a subset of records are still considered to be full data matching jobs because the data to be checked does not depend on earlier data matching.