Configuration Guide

Back Next

Match Rules

A match rule defines the criteria by which

Informatica MDM Hub

determines whether two records in the base object might be duplicates. Match rules can be based on match columns or primary keys.

Type	Description
Match column rules	Used to match base object records based on the values in columns you have defined as match columns, such as last name, first name, address1, and address2. This is the most commonly-used method for identifying matches.
Primary key match rules	Used to match records from two systems that use the same primary keys for records. It is uncommon for two different source systems to use identical primary keys. However, when this does occur, primary key matches are quick and very accurate.

Both kinds of match rules can be used together for the same base object.

The match rule you specify can be one of the following types:

Rule Type	Description
Exact match	Values must match exactly, or the special case must match exactly, such as null matches null. The processing for exact match takes place primarily on the database server.
Fuzzy match	Values are not an exact match but similar to the value being matched against. Matches are determined by the match tokens that are shared by some values and this depends on the population. For example, Robert, Rob, and Bob in English speaking populations, for the match purpose of Name, may have the same match token value. A fuzzy match is primarily processed on the application server.
Filtered match	Similar to exact match. The exact match rule is changed to a type Filtered, and the fuzzy match engine is used to achieve the same results as you would with an exact match rule. Filtered match rules use the search level of Narrow, because the fuzzy matching must be narrow enough for the results to be the same as that of an exact match. The processing for filtered match takes place primarily on the application server.