To attach a Match Rule to a Data Model, do the following.
In the MDM Repository tree view, open the Data Model to which you want to attach the Match Rule.
Select the entity and, in the Properties view, open the Rules tab.
In the Matching Rule section, select the Match Rule you want to attach to this Data Model from the drop-down list.
If needed, click Open Match Rule to open and view the details of the Match Rule.
In the table, map each Match Key to the corresponding Entity element using the selection window.
If you want to attach a match rule with multiple rules to a data model, make sure each match key is mapped to an entity element correctly in each rule within the match rule.
You can select any simple type elements at the root level from a single entity and the entities linked by a foreign key (if any) defined in the previous entity. Note that the survivorship function does not take effect on the elements selected from those foreign key entities. For an example of defining a match rule with match keys mapped to simple type elements from multiple entities, see An example of defining a match rule with match keys mapped to simple type elements from multiple entities.
Once a data model is attached with a match rule mapped to multiple entities, the integrated matching performance might be affected if a large number of data records pertain to one of the entities since the query with JOIN operations on large tables will be time-consuming for database.
Click the [+] button and, from the [Select Element] dialog box that opens, select one element to be used as the blocking key.
Alternatively, select the Use the built-in "Blocking Key" column check box to use the built-in blocking key which has been predefined in the Staging Area and according to which you want to partition the processed data in blocks. A built-in blocking key is defined using a Job (with a single column or the transformation of multiple columns). The Job can connect directly to the database to update this built-in blocking key.
Defining a blocking key is not mandatory but strongly advisable. Integrated Matching performs faster when the matching defines a blocking key, thanks to parallelization. For the best performance, the database column used as a blocking key should be indexed.
Save your changes.