Virtual MDM data model division of tables
The tables in a virtual MDM database can be divided into basic categories. Some of the tables are used for several different purposes, but can still be thought of in terms of an overall component functional architecture.
The table categories are described in the following table.
| Category | Description |
|---|---|
| Audit | These tables contain auditing data. This data identifies who accessed what data and who modified what data. Auditing can track data changes that are made by internal system users and updates from source systems. Most audit tables begin with the prefix “mpi_aud…”. |
| Algorithm configuration | Algorithm configuration tables contain data that is related to the setup of an algorithm for an entity. |
| Analytic | Analytic tables store bucket and entity analysis information |
| Base configuration | Base configuration tables contain data about the initial startup of the operational server. |
| Entity-to-member | These relationship tables store data that is related to the linking of a member to an entity. By tracking entity relationships in separate tables, MDM can link and unlink members without adding unnecessary fields. This design also provides for review of entity linkage history. Entity relationship tables begin with “mpi_ent…” and often end with a suffix that represents the entity type (for example, _id for Identity or _hh for Household). |
| Event notification | These tables support notification to downstream systems of events that happen in MDM. |
| Metadata | These tables define data types and values that are provided by various source systems. |
| Member | Member tables contain data that is explicitly associated with members in the virtual MDM database. Member data is stored by segment (for example, Name, Date, ID, and so on). Member tables begin with “mpi_mem…”. |
| Relationship | These tables contain the information that define member relationships. Relationship tables begin with “mpi_rel...”. |
| Runtime configuration | These tables contain information that is used by the operational server for applications that connect at run time. |
| Tag | These tables provide the definitions for tag processing. |
| Workflow task | These tables contain data that is associated with defined task types and their corresponding states. |