Table of Contents

Search

  1. Preface
  2. Part 1: Introduction
  3. Part 2: Configuring Hub Console Tools
  4. Part 3: Building the Data Model
  5. Part 4: Configuring the Data Flow
  6. Part 5: Executing Informatica MDM Hub Processes
  7. Part 6: Configuring Application Access
  8. Appendix A: MDM Hub Properties
  9. Appendix B: Viewing Configuration Details
  10. Appendix C: Row-level Locking
  11. Appendix D: MDM Hub Logging
  12. Appendix E: Table Partitioning
  13. Appendix F: Collecting MDM Environment Information with the Product Usage Toolkit
  14. Appendix G: Glossary

Non-equal Matching

Non-equal Matching

Use the Non-equal Matching option in match rules to prevent equal values in a column from matching each other. Non-equal Matching applies only to exact-match columns.
Non-equal Matching and Segment Matching are mutually exclusive. If one is selected, then the other cannot be selected.
You can think about the Non-equal Matching option as an anti-match option. The match result when the option is enabled is the opposite of the match result when the option is disabled.
You can use Non-equal Matching to match a record with a fuzzy organization name column and an exact, non-equal organization type column. Even though organization names are identical, the records will match only if the organization types are not identical.

Non-equal Matching without NULL Matching

First consider the effect of the Non-equal Matching option when NULL matching is disabled. As you can see from the following table, the NULL values never match, and the equal values match. With the Non-equal Matching option is enabled, the opposite is true: all the NULL values match and equal values do not match.
The following table shows simple match results before and after Non-equal Matching is enabled:
Values
Non-equal Matching=False
Non-equal Matching=True

    Record 1 = NULL

    Record 2 = "Fred"

No match
Match

    Record 1 = NULL

    Record 2 = NULL

No match
Match

    Record 1 = "Bill"

    Record 2 = "Fred"

No match
Match

    Record 1 = "Fred"

    Record 2 = "Fred"

Match
No match

Non-equal Matching with NULL Matches NULL

Similarly, when you enable the Non-equal Matching option with the NULL Matches NULL option, the match results switch to the opposite results.
The following table shows the match results before and after Non-equal Matching is enabled with NULL Matches NULL:
Values
Non-equal Matching=False
NULL Matches NULL=True
Non-equal Matching=True
NULL Matches NULL=True

    Record 1 = NULL

    Record 2 = "Fred"

No match
Match

    Record 1 = NULL

    Record 2 = NULL

Match
No match

    Record 1 = "Bill"

    Record 2 = "Fred"

No match
Match

    Record 1 = "Fred"

    Record 2 = "Fred"

Match
No match

Non-equal Matching with NULL Matches Non-NULL

When you enable the Non-equal Matching option with the NULL Matches Non-NULL option, the match result switches to the opposite result. In one circumstance, the records with NULL values do not match. See the explanation below the table.
The following table shows the match results before and after Non-equal Matching is enabled with NULL Matches Non-NULL:
Values
Non-equal Matching=False
NULL Matches Non-NULL=True
Non-equal Matching=True
NULL Matches Non-NULL=True

    Record 1 = NULL

    Record 2 = "Fred"

Match
No match

    Record 1 = NULL

    Record 2 = NULL

No match
Match
*

    Record 1 = "Bill"

    Record 2 = "Fred"

No match
Match

    Record 1 = "Fred"

    Record 2 = "Fred"

Match
No match
* When a match rule uses Filtered Exact, the result is a match. However, when a match rule uses Exact, the result is no match.

0 COMMENTS

We’d like to hear from you!