NME Unification Repository Tables

The tables are created automatically per repository (Extended Unification). When the VLDB persistence/logical transaction is used, all the following tables are prefixed based on a prefix definition in nme-config.xml: [prefix]. Note that only Unification Extended should be used in iWay MDS-based configurations. Also note that the NME Extended Unification repository format will be used, and it is different from the standalone Extended Unification repository format.

Repository Structure	Description
Main Tables
[prefix] [repository_name]_DATA	Main table DATA. The table stores all data columns, input, and output timestamps. The values are stored in varchar(4000) or blobs (text), semicolon separated, structure of the file is described in the _FORM table.
[prefix] [repository_name]_FORM	Main table FORM. Keeps repository structure. You can keep more repository structures. The structure is used for the validation of the Repository format. When the format is different, execution fails during validation.
[prefix] [repository_name]_GIDS	Main table GIDS. Contains the mapping between candidate group IDs and candidate grouping keys for the Unify operation.
[prefix] [repository_name]_KEYS	Main table KEYS. Contains a list of candidate grouping keys and group IDs for all records.
[prefix] [repository_name]_META	Main table META. Keeps basic metadata about a repository such as timestamps, and so on. Contains a description of the repository, maximum group ID assigned, number of records, and internal settings of the repository.
Working Tables
[prefix] [repository_name]_WDKEY	Working table.
[prefix] [repository_name]_WGID	Working table. Contains a list of group IDs for the operation and process necessary for the expansion.
[prefix] [repository_name]_WKEY	Working table. Contains a list of candidate grouping keys for the operation and process necessary for the expansion.
[prefix] [repository_name]_WPK	Working table. Contains a list of primary keys for the operation and process necessary for the expansion.

Repository Structure

Description

Main Tables

[prefix] [repository_name]_DATA

Main table DATA.

The table stores all data columns, input, and output timestamps.
The values are stored in varchar(4000) or blobs (text), semicolon separated, structure of the file is described in the _FORM table.

[prefix] [repository_name]_FORM

Main table FORM.

Keeps repository structure. You can keep more repository structures.
The structure is used for the validation of the Repository format. When the format is different, execution fails during validation.

[prefix] [repository_name]_GIDS

Main table GIDS.

Contains the mapping between candidate group IDs and candidate grouping keys for the Unify operation.

[prefix] [repository_name]_KEYS

Main table KEYS.

Contains a list of candidate grouping keys and group IDs for all records.

[prefix] [repository_name]_META

Main table META. Keeps basic metadata about a repository such as timestamps, and so on.

Contains a description of the repository, maximum group ID assigned, number of records, and internal settings of the repository.

Working Tables

[prefix] [repository_name]_WDKEY

Working table.

[prefix] [repository_name]_WGID

Working table.

Contains a list of group IDs for the operation and process necessary for the expansion.

[prefix] [repository_name]_WKEY

Working table.

Contains a list of candidate grouping keys for the operation and process necessary for the expansion.

[prefix] [repository_name]_WPK

Working table.

Contains a list of primary keys for the operation and process necessary for the expansion.

Repository Name Convention

The repository name is defined as part of the Extended Unification step. In case of an iWay MDS project, the repository name can be the same as the related entity name.

For example:

PARTY
ADDRESS

To distinguish data tables and unification tables, the prefix REP, followed by the entity name, should be used.

For example:

REP_PARTY
REP_ADDRESS