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

Database Schemas

To manage and store essential data, MDM Server uses several dedicated database schemas. These schemas are defined in the application.properties file, see MDM Server Application Properties, section Data source configuration.

These infrastructural settings need to be defined only once and cannot be defined both in the application.properties and mdm.runtimeConfig files.

The following table lists the necessary database schemas along with their descriptions.

Name Name in the application.properties file Description

Name	Name in the application.properties file	Description
`mdc`	`mdc_db`	Persistent storage for master and instance records, matching data, tasks and drafts data, history data. To learn more, see MDM Storage.
`eh`	`eh_db`	Persistent storage of data for event handlers (referenced in the `nme-event_handler.gen.xml`), automated tasks, and history plugin.
`orchestration`	`orchestration_db`	Persistent storage of data for the orchestration workflow (EWF), scheduler, and custom orchestration tables. Referenced in the `mdm.serverConfig` file.
`ai_matching`	/	Storage of data related to AI Matching processes.

mdc

mdc_db

Persistent storage for master and instance records, matching data, tasks and drafts data, history data. To learn more, see MDM Storage.

eh

eh_db

Persistent storage of data for event handlers (referenced in the nme-event_handler.gen.xml), automated tasks, and history plugin.

orchestration

orchestration_db

Persistent storage of data for the orchestration workflow (EWF), scheduler, and custom orchestration tables. Referenced in the mdm.serverConfig file.

ai_matching

Storage of data related to AI Matching processes.

In case you use the external database schema, we recommend migrating it to the orchestration schema.

Was this page useful?