If you can't find the product or version you're looking for, visit support.ataccama.com/downloads

MDM Storage

MDM Storage is created automatically when the server starts for the first time, and the generation of the structures for the storage is based on the defined model. The MDM Storage structure is transparent to users while the implementation details of the structure are completely hidden. This is why direct access to the MDM Storage is not allowed and why we recommend using only the official APIs for that purpose.

MDM storage includes a repository of cleansed, matched, and mastered data consisting of the following:

The current data repository stores the instance records, or source records, from different source systems, as well as master records computed based on a consolidation process or authored directly to a master layer.

Storing data from the source systems has a critical purpose and provides many benefits, for example, it allows incremental data processing. All records from the source systems are stored in their cleansed form, which allows systems to retrieve cleansed versions of their own records, and comparison against existing data is done when receiving updates.

This makes it possible to efficiently handle updates in MDM and cross-system distribution of source records.
- The Matching Key tables for all matched entities. These tables enable incremental matching, as well as identification of records when used as a service.
- Other technical tables.
  
  For more details about the data layers in the MDM Model, see MDM Model.
The historical data repository stores previous versions of both instance and master data.

History contains data in a defined scope (specified entities, specified columns) and in defined frequency (all changes vs. change triggered by some specified columns). Data is stored as BLOBs by default, unless specified otherwise (especially for the purpose of searching through data history).

The MDM storage relies on a database. Although MDM is database platform-independent, we recommend using PostgreSQL as your storage solution. For an overview of other options and their limitations, see Supported Third-Party Components.

While the MDM storage is limited in terms of the databases supported, when it comes to connected systems, MDM can integrate with all databases commonly used in the industry as long as there is a JDBC driver available for them.

Was this page useful?