Communities
A collaborative platform to connect and grow with like-minded Informaticans across the globe
Product Communities
Connect and collaborate with Informatica experts and champions
Discussions
Have a question? Start a Discussion and get immediate answers you are looking for
User Groups
Customer-organized groups that meet online and in-person. Join today to network, share ideas, and get tips on how to get the most out of Informatica
Get Started
Community Guidelines
Knowledge Center
Troubleshooting documents, product guides, how to videos, best practices, and more
Knowledge Base
One-stop self-service portal for solutions, FAQs, Whitepapers, How Tos, Videos, and more
Support TV
Video channel for step-by-step instructions to use our products, best practices, troubleshooting tips, and much more
Documentation
Information library of the latest product documents
Velocity (Best Practices)
Best practices and use cases from the Implementation team
Learn
Rich resources to help you leverage full capabilities of our products
Trainings
Role-based training programs for the best ROI
Certifications
Get certified on Informatica products. Free, Foundation, or Professional
Product Learning Paths
Free and unlimited modules based on your expertise level and journey
Resources
Library of content to help you leverage the best of Informatica products
Tech Tuesdays Webinars
Most popular webinars on product architecture, best practices, and more
Product Availability Matrix
Product Availability Matrix statements of Informatica products
SupportFlash
Monthly support newsletter
Support Documents
Informatica Support Guide and Statements, Quick Start Guides, and Cloud Product Description Schedule
Product Lifecycle
End of Life statements of Informatica products
Ideas
Events
Change Request Tracking
Marketplace
English
  • Informatica Data Quality 10.5.2
  • All Products

Table of Contents

Search

  1. Preface
  2. Introduction to Transformations
  3. Transformation Ports
  4. Transformation Caches
  5. Address Validator Transformation
  6. Aggregator Transformation
  7. Association Transformation
  8. Bad Record Exception Transformation
  9. Case Converter Transformation
  10. Classifier Transformation
  11. Comparison Transformation
  12. Consolidation Transformation
  13. Data Masking Transformation
  14. Data Processor Transformation
  15. Decision Transformation
  16. Duplicate Record Exception Transformation
  17. Expression Transformation
  18. Filter Transformation
  19. Hierarchical to Relational Transformation
  20. Java Transformation
  21. Java Transformation API Reference
  22. Java Expressions
  23. Joiner Transformation
  24. Key Generator Transformation
  25. Labeler Transformation
  26. Lookup Transformation
  27. Lookup Caches
  28. Dynamic Lookup Cache
  29. Macro Transformation
  30. Match Transformation
  31. Match Transformations in Field Analysis
  32. Match Transformations in Identity Analysis
  33. Normalizer Transformation
  34. Merge Transformation
  35. Parser Transformation
  36. Python Transformation
  37. Rank Transformation
  38. Read Transformation
  39. Relational to Hierarchical Transformation
  40. REST Web Service Consumer Transformation
  41. Router Transformation
  42. Sequence Generator Transformation
  43. Sorter Transformation
  44. SQL Transformation
  45. Standardizer Transformation
  46. Union Transformation
  47. Update Strategy Transformation
  48. Web Service Consumer Transformation
  49. Parsing Web Service SOAP Messages
  50. Generating Web Service SOAP Messages
  51. Weighted Average Transformation
  52. Window Transformation
  53. Write Transformation
  54. Appendix A: Transformation Delimiters

Developer Transformation Guide

Developer Transformation Guide

Back Next

Master Data Analysis

Master Data Analysis

When you analyze two data sources in the Match transformation, you must identify a source as the master data set. The transformation compares data values from each record in the data set that you specify with the corresponding values in every record in the second data set.
In many organizations, a master data set constitutes a permanent, high-quality data store. Before you add records to a master data set, use the Match transformation to verify that the records do not add duplicate information to the master data.

Master Data Example

A bank maintains a master data set of customer account records. The bank updates the master data set every day with records that identify new customer accounts. The bank uses a duplicate analysis mapping to verify that the new records do not duplicate the customer information in the master data set. The master data set and the new account tables have a common structure, and the tables use the same type of database. Therefore, the bank can reuse the duplicate analysis mapping each time it needs to update the master data set.

Directionality in Master Data Set Analysis

The Match transformation compares records from one data set to another in a single direction. The transformation compares each record in the master data set to all of the records in the second data set. The transformation does not compare each record in the second data set to all of the records in the master data set. Therefore, the selection of the master data set can affect the results of the match analysis.
The following table shows two data sets that you can compare in identity match analysis:
Data Set 1
Data Set 2
Alex Bell
Alexander Bell
Alexander Graham Bell
Thomas Edison
Alva Edison
Nicola Tesla
Marie Curie
Irene Joliot Curie
Dorothy Crowfoot
Dorothy Hodgkin
If you select Data Set 1 as the master data set and you select the
Best Match
 output option, the output includes the following records:
  • Alex Bell, Alexander Bell
  • Alexander Graham Bell, Alexander Bell
If you select Data Set 2as the master data set and you select the
Best Match
 output option, the output includes the following records:
  • Alexander Bell, Alex Bell
When Data Set 2 is the master data set, the transformation cannot match Alexander Bell and Alexander Graham Bell, because Alexander Bell already matches Alex Bell in the output data.
0 COMMENTS
We’d like to hear from you!