SQL views for InfoSphere Information Governance Dashboard

You can use the SQL views to query objects in the InfoSphere® Information Server metadata repository that might otherwise not be accessible to SQL queries.

The views are grouped in schemas for the following domains: common metadata, data quality, and information governance.

Warning: Do not use SQL views to update objects in the metadata repository. Trying to use the SQL views to write to the metadata repository might damage the contents of the metadata repository.

HTML documentation and entity definitions

You can access the HTML documentation for the schemas from the following HTML document: Descriptions of all objects and properties that are used in the SQL views.

Important: Make sure you have patch CMS RU2 installed on your system for up-to-date SQL views.
The SQL views are based on tables in the metadata repository. These tables logically belong to different IBM® InfoSphere Information Server components. The SQL views of IBM InfoSphere Information Governance Dashboard reflect these table sources by grouping views into corresponding schemas:
  • CMVIEWS (metadata that is common to various components)
  • IAVIEWS (IBM InfoSphere Information Analyzer)
  • IGVIEWS (IBM InfoSphere Information Governance Catalog)
  • REMVIEWS (metadata for exception management reports, remediation, and IBM Stewardship Center)

The SQL views are grouped accordingly in the HTML documentation. The HTML documentation describes the individual entities and relationships among them. Some of these relationships connect entities that belong to different schemas, in which case the description of the entity that is external to the current schema is represented by a placeholder with the same name as the entity. However, this placeholder shows only a subset of the external entity's properties, excluding, for example, foreign keys linking to entities within the schema in which this external entity is defined. To see the full definition of this entity, you must look up the entity definition in the schema to which it belongs.

An example of this situation concerns the entity MAINOBJECT. Its placeholder in the documentation for the IGVIEWS schema does not show foreign keys to other entities in the CMVIEWS schema, such as the PRINICPAL entity. These foreign keys are displayed only in the definition of MAINOBJECT in the schema to which it belongs, the CMVIEWS schema.

Views

The following views are used to query objects in the metadata repository.
CMVIEWS
Contains views of a subset of common metadata object types that represent database metadata that is imported by bridges or connectors. These views describe hosts, databases, schemas, tables, views, stored procedures, and columns. CMVIEWS contains general views of notes, users, and stewardship assignments.
IAVIEWS
Contains views of object types from the data quality domain that are created in InfoSphere Information Analyzer. The object types include projects, data rules, data rule sets, data rule definitions, and data rule set definitions. The schema also contains many views that are necessary to link analysis objects to other objects, such as database columns.
IGVIEWS
Contains views of object types from the information governance domain that are created in IBM InfoSphere Information Governance Catalog, including categories, terms, labels, information governance policies, and information governance rules. The schema also includes views that link information governance objects to the data rules that implement them and to other assets.
REMVIEWS
Contains views of objects for exception management, such as exception sets, their change history, and their properties.