Table of Contents


  1. Introduction
  2. Configuring Hub Console Tools
  3. Building the Data Model
  4. Configuring the Data Flow
  5. Executing Informatica MDM Hub Processes
  6. Configuring Application Access
  7. MDM Hub Properties
  8. Viewing Configuration Details
  9. Search with Solr
  10. Row-level Locking
  11. MDM Hub Logging
  12. Table Partitioning
  13. Collecting MDM Environment Information with the Product Usage Toolkit
  14. Glossary

Match/Search Strategy

Match/Search Strategy

Select the match/search strategy to specify the reliability of the match versus the performance you require. Select one of the following options.
Strategy Option
Probabilistic match that takes into account spelling variations, possible misspellings, and other differences that can make matching records non-identical. This is the primary means of matching data in a base object. Referred to in this document as
fuzzy-match base objects
If you specify a Fuzzy match/search strategy, you must specify a fuzzy match key.
Matches only records with identical values in the match column(s). If you specify an exact match, you can define only exact-match columns for this base object (exact-match base objects cannot have fuzzy-match columns). Referred to in this document as
exact-match base objects
An exact strategy is faster, but an exact match will miss some matches if the data is imperfect. The best option to choose depends on the characteristics of the data, your knowledge of the data, and your particular match and consolidation requirements.
Certain configuration settings in the Match / Merge Setup tab apply to only one type of base object. In this document, such features are indicated with a graphic that shows whether it applies to fuzzy-match base objects only (as in the following example), or exact-match base objects only. No graphic means that the feature applies to both.
The match / search strategy is configured at the base object level.


We’d like to hear from you!