Different types of tables and purpose

[Former Member]

Hi,

Could someone explain me the different types of tables an what data they store.

Sonali

[Former Member · Accepted solution]

Hi Sonali,

You can refer to the below links.

Hope it helps.

Thanks,

Minaz

[Former Member]

Hi Sonali,

If you query has been resolved then please mark this question as answered so that others having same problem can refer your thread.

Regards,

Varun

[Former Member]

Hi Sonali,

In MDM Mainly we have 5 Types of Tables.

1. Main Table : Main Table is allways a "Flat table".

2. Sub Tables : 3 Types (Hierarchy, Taxonomy, Qualified Tables)

In Hierarchy table information is in hierarcy. parent and child relationship

In taxonomy table information is in Categories and subcategories.

In Qualified table information is in lookup tables.

3. Object Tables

Images, Sounds, Video's, Binary Objects, Text Blocks, Text HTML's, PDFs, Copy Blocks.

Images : Stores Image files

Sounds : Stores Sound files

Video's : Stores video files.

Binary Objects :Stores other binary object files.

Text Blocks : Stores blocks of text.

PDFs : Stores PDF fiels.

Text HTML's : Stores blocks of text interpreted as HTML's

Copy Blocks : Stores blocks of text interpreted as copy

4. Special tables

Image variants, Masks, Families, Relationship's, Workflow's, Named Searches,

Data groups, Validation Groups.

Image Variants: Define the structure and format of each of the variant's each image.

Masks : Mask acts like a Stencil. View of any table.

Families: Further partition main table records in each category into smaller groups based upon the

values of other frields and/or attributes .

Relationship's : To define each of the different record-level relationships.

Workflow's : Stores the worflows of an MDM Repository.

Named Searches: A named search is a static snapshot of the search selections that were in

effect when the named search was created. Each record in the

Named Searches table returns a subset of main table records.

Data groups: Stores the hierarchy of data groups used to break the entire set of objects in the MDM

repository into manageable subgroups.

Validation Groups: Stores the hierarchy of validation groups used to organize multiple validations

for subsequent execution as a group.

5. System Tables ( These tables used to implement MDM Repository Security and Access control )

Roles, Users, Connections, Change Tracking, Remote Systems, Ports, Links, XML Schemas,

Reports, Logs.

Roles : Each role can selectively grant or deny access to any MDM function and to any table or field.

Users : Each user can have one or more roles.

Connections : Contains an entry for each MDM client application currently connected to the

Repository. ( we cant see in MDM Client)

Change Tracking : Allows you to specify the fields for which adds, modifies, and deletes should be

tracked and stored in the Change Tracking table.

Remote Systems : Used to define the different remote systems for import and export. Each specifies

whether it supports inbound, outbound, or both. (We can't see in MDM Client)

Ports : Used to encapsulate the logistical and configuration info for inbound and outbound processing

of MDM data, for consolidation and distribution respectively. (We can't see in MDM Client)

Links : Used to specify the URLs that can be used as the target of an embedded browser in the Web

tab in the MDM Client. (We can't see in MDM Client)

XML Schemas : Used to identify the XML schemas for import and syndication. Each XML schema is

the name of an .xsd file. (We can't see in MDM Cleint).

Reports : Contains an entry for each report file generated by the various MDM repository operations,

which can be accessed and viewed by the MDM Console user.(We can't see in MDM Client)

Logs : Contains an entry for the log files generated by the MDM Server, which can be accessed and

viewed by the MDM Console user. (We can't see in MDM Client).

These are the tables in MDM and there use.

Thanks

Kiran

[Former Member]

hi Sonali,

These are the different types of tables in MDM

Flat Tables : It is a simple table consisting of record and fields ( rows and column) .

Hierarchy Table : A hierarchy table organizes information in a hierarchy, where each record is related to a parent record (even if the only parent is the root) and may also be related to sibling records and/or child records.

Taxonomy Table : A taxonomy is the classification scheme that defines the categories and subcategories that apply to a collection of records. Categorizing records enables you to isolate subsets of records for various organizing, searching, editing and publishing purposes.

Qualified Table : A qualified table in MDM stores a set of lookup records,and also supports qualifiers, u201Csubfieldsu201D that apply not to the qualified table record by itself, but rather to each association of a qualified table record with a main table record. MDM supports multiple simultaneous qualified tables.

Tables are also Categorized as Object Tables like :

Images : This table is for storing Images

Sounds : This table is for storing Sound File.

Videos : This table is for storing Video Files .

Binary Objects : This table is for storing Binary Objects.

Text Blocks : This table is for storing block of text.

Copy Blocks : This table is for storing block of text interpreted as a Copy.

Text HTML`s : This table is for storing block of text interpreted as a HTML.

PDFs : This table is for storing PDF files.

There are various types of Special Tables , i have mentioned below:

Image Variants : Used to define the structure

and format of each of the variants for each image. Each variant is a modified version derived from an original image; the original image is never modified.

Masks : In this defined subset of records are included in Mask i.e. in any scenario whether new records are added or deleted in the repository the records in the Mask remains the same unless edited by the user.

Families : Used to further partition main table records in each category into smaller groups based upon the values of other fields and/or attributes.

Relationships : Used to define each of the different record-level relationships. Each relationship can be either bidirectional (sibling) or unidirectional (parent-child).

Workflows : Stores the workflows of an MDM repository, where each workflow is stored as a record in the table.

Name Searches : Unlike Masks in case of Name search there are again a defined set of records but those records are selected on the basis of Search Selection. In this case if a record is added then the record is checked whether it fulfills the particular search criteria if it does than it is added to the Name serach else not.

Data Groups : Stores the hierarchy of data groups used to break the entire set of objects in the MDM repository into manageable subgroups.

There are various types of System Tables :

Roles : A single table named Roles. One of three tables used to implement MDM repository security and access control. Each role can selectively grant or deny access to any MDM function and to any table or field. This table is managed in the MDM Console and is not visible in the MDM Client.

Users : A single table named Users. One of three tables used to implement MDM repository security and access control. Each user can have one or more roles. This table is managed in the MDM Console and is not visible in the MDM Client.

Connections : A single table named Connections. One of three tables used to implement MDM repository security and access control. Contains an entry for each currently connected MDM client application, which can be terminated by the MDM Console user. This table is not visible in the MDM Client.

Change Tracking : A single table named Change Tracking. Allows you to specify the fields for which adds, modifies, and deletes should be tracked and stored in the Change Tracking table.

Remote Systems : A single table named Remote Systems. Used to define the different remote systems for import and export. Each specifies whether it supports inbound, outbound, or both. This table is managed in the MDM Console and is not visible in the MDM Client.

Ports : A single table named Ports. Used to encapsulate the logistical and configuration info for inbound and outbound processing of MDM data, for consolidation and distribution respectively. This table is managed in the MDM Console and is not visible in the MDM Client.

Links : A single table named Links. Used to specify the URLs that can be used as the target of an embedded browser in the Web tab in the MDM Client. This table is managed in the MDM Console and is not visible in the MDM Client.

XML Schema : A single table named XML Schemas. Used to identify the XML schemas for import and syndication. Each XML schema is the name of an .xsd file. This table is managed in the MDM Console and is not visible in the MDM Client.

Reports : A single table named Reports. Contains an entry for each report file generated by the various MDM repository operations, which can be accessed and viewed by the MDM Console user. This table is not visible in the MDM Client.

Logs : A single table named Logs. Contains an entry for the log files generated by the MDM Server, which can be accessed and viewed by the MDM Console user. This table is not visible in the MDM Client.

In MDM SP06 5.5 we can have only one main table, but in MDM 7.1 version we can maintain many main tables.

Rewards points if helpful

Regards,

Vijay

[Former Member]

Hi Sonali,

Different types of tables in MDM:

Main table: The main table consists of the primary information about each main table record.It reflects the most important object; in a product repository, it would be the product including a field for each general valid piece of information.

Sub-Tables: A subtable is usually used as a lookup table to define the set of legal values to which a corresponding lookup field in the main table can be assigned; these tables hold the lookup information.

Object tables: Object tables, including the Images, Sounds, Videos, Binary Objects, Text Blocks, Copy Blocks, Text HTMLs, and PDFs tables, are a special type of lookup subtable.Each object table is used to store a single type of object.

Special tables: Includes masks, families, image variants, relationships, workflows, named searches, data groups and validation groups table.

System tables: System tables appear under the Admin node in the Console Hierarchy and include Roles, Users, Connections, Change Tracking, Remote Systems, Ports, Links, XML Schemas, and Reports, and Logs.

Regards,

Varun

Edited by: Varun Agarwal on Oct 14, 2008 3:27 PM