0 / 0
Reporting tables for Watson Knowledge Catalog
Reporting tables for Watson Knowledge Catalog

Reporting tables for Watson Knowledge Catalog

Reporting data for Watson Knowledge Catalog is stored in SQL tables in PostgreSQL, Db2 database. You can use the descriptions of the tables to better understand the reporting data and to generate more meaningful reports.

Each table description contains the list of table columns with short descriptions and the CREATE TABLE SQL statement. In some cases, ALTER TABLE and CREATE INDEX statements are provided.

Each of these tables has a history table that is associated with it. The name of a history table starts with the prefix hist_, followed by the table name.

In PostgreSQL SQL tables, use the f_trig_<table_name> function to populate the tables with appropriate data. The function is defined in the following way:

CREATE OR REPLACE
FUNCTION f_trig_<table_name>() RETURNS TRIGGER AS $$
DECLARE
BEGIN
    IF
            (TG_OP = 'DELETE') THEN OLD.tech_end = CURRENT_TIMESTAMP;

INSERT
    INTO
    hist_<table_name>
VALUES (OLD.*);

RETURN OLD;

ELSIF (TG_OP = 'UPDATE') THEN OLD.tech_end = CURRENT_TIMESTAMP;

NEW.tech_start = CURRENT_TIMESTAMP;

INSERT
    INTO
    hist_<table_name>
VALUES (OLD.*);

RETURN NEW;
END
IF;
END;

$$ LANGUAGE 'plpgsql'

To better understand the replationships between the SQL tables that store the reporting data, see Data model for Watson Knowledge Catalog reporting. The list of tables is as follows:

Subject area Table name Description
Workspaces containers Catalogs and projects that are created.
Workspaces projects A project and its members.
Workspaces container_assets The assets that are defined in a catalog or project.
Workspaces container_data_assets The data assets that are defined in a catalog or project.
Workspaces container_data_asset_columns The columns in a data asset.
Workspaces data_asset_column_tags The tags that are associated with the columns.
Workspaces asset_collaborators A list of all the members of an asset.
Workspaces container_members A list of all the members of a catalog or project.
User Profiles user_profiles A list of all the users of a catalog or project.
Asset relationships asset_artifact_relations The associations between asset and governance artifacts.
Asset relationships container_assets_associations The relationships between the catalog assets.
Asset relationships asset_tags The tags that are associated with an asset.
Asset relationships governance_artifact_container_associations The governance artifact, which is associated with a catalog asset.
Asset relationships data_asset_column_artifact_associations The governance artifacts, which are associated with the column of the data asset.
Tags Tags The tags that are defined.
Rules enforcement_rules The enforcement rules (data protection rules) that are defined.
Categories categories The governance categories that are defined.
Categories category_collaborators A list of all collaborators of a category.
Categories category_tags The tags that are associated with a category.
Categories category_associations The relationships between categories.
Governance artifacts governance_artifacts The governance artifacts that are defined in the system that are in the published state.
Governance artifacts governance_artifact_stewards A list of stewards that are assigned to a published artifact.
Governance artifacts governance_artifact_associations The relationships between the governance artifacts.
Governance artifacts artifact_tags The tags that are associated with an artifact.
Artifact relationships secondary_category_associations A list of secondary categories to which an artifact is assigned.
Artifact relationships business_term_associations The relationships between business terms.
Artifact relationships data_class_associations The relationships between data classes.
Artifact relationships policy_associations The relationships between policies.
Artifact relationships reference_data_set_associations The relationships between reference data sets.
Artifact relationships classification_associations The relationships between classifications.
Artifact relationships governance_rule_associations The relationships between governance rules.
Artifact relationships artifact_enforcement_rule_associations The implicit relationships between a governance artifact and enforcement rules.
Data quality scores asset_quality_score_problems The quality problems for the data asset.
Data quality scores asset_columns_quality_score_problems The quality problems for the data asset column.
Metadata imports and enrichments metadata_imports Metadata import information.
Metadata imports and enrichments metadata_import_executions The scheduled time of the metadata import job.
Metadata imports and enrichments metadata_enrichments Metadata enrichments information.
Data quality rules dq_problems The quality problems defined for a project.
Data quality rules dq_dimensions The quality dimensions for the rule.
Data quality rules dq_rule_definitions The data quality rule definition.
Data quality rules dq_rules_defs Data Quality Rule Definitions.
Data quality rules dq_rules The data quality rule information.
Data quality rules dq_rule_bindings The rule bindings for the data quality rule.
Data quality rules dq_rule_execution The scheduled time for the data quality rule job.
Customizations category_custom_roles The custom category roles.
Customizations glossary_custom_relationship_def The custom relationship definitions.
Customizations glossary_ca_attr_artifact_type_assoc The supported artifact types for custom attribute definition.
Customizations glossary_custom_relationship_nodes The source and target artifact type for custom relationship definitions.
Customizations glossary_custom_attr_def The custom attribute definitions.
Customizations glossary_ca_enum_list the custom attribute definitions of ENUM type.
Customizations governance_artifact_custom_attr_values The custom attribute values.
Artifact relationships artifact_category_associations The relationships between governance artifact and category.
Workflow workflow_types The workflow types.
Workflow workflow_templates The workflow templates.
Workflow workflow_configurations The workflow configurations.
Workflow workflows The workflows.
Workflow workflow_tasks The workflow tasks.

containers table

This table contains information about the catalogs and projects that are created.

This table has the following columns:

  • container_id - The identifier of the catalog or project.
  • container_type - Specifies whether the type of the workspace is a catalog or project.
  • name - The name of the catalog or project.
  • description - The description of the workspace.
  • is_governed - Specifies whether the catalog is governed or not. Applicable to catalogs only.
  • created_by - The identifier of the user that created the workspace.
  • created_on - The timestamp when the workspace was created.

Postgres

CREATE TABLE statement:

create table containers(container_id varchar(36) not null,
container_type varchar(16) not null,
name varchar(256) not null,
description clob,
is_governed boolean not null,
created_by varchar(128) not null,
created_on timestamp(12) not null,
tech_start TIMESTAMP(12) not null IMPLICITLY HIDDEN generated always as row begin,
tech_end TIMESTAMP(12) not null IMPLICITLY HIDDEN generated always as row
end,
ts_id TIMESTAMP(12) not null generated always as transaction start ID,
primary key(container_id),
period SYSTEM_TIME (tech_start,
tech_end) )

Db2

CREATE TABLE statement:

CREATE TABLE containers(container_id varchar(36) NOT NULL,
container_type varchar(16) NOT NULL,
name varchar(256) NOT NULL,
description clob,
is_governed boolean NOT NULL,
created_by varchar(128) NOT NULL,
created_on timestamp(12) NOT NULL,
tech_start TIMESTAMP(12) NOT NULL IMPLICITLY HIDDEN GENERATED ALWAYS AS ROW BEGIN,
tech_end TIMESTAMP(12) NOT NULL IMPLICITLY HIDDEN GENERATED ALWAYS AS ROW END,
ts_id TIMESTAMP(12) NOT NULL GENERATED ALWAYS AS TRANSACTION START ID,
PRIMARY KEY(container_id),
PERIOD SYSTEM_TIME (tech_start,
tech_end) )

projects table

This table contains information about a project and its members.

This table has the following columns:

  • project_id - The identifier of the project.
  • project_name - The name of the project.
  • enforce_members - Specifies whether the project members are scoped to the account or SAML of the creator.

Postgres

CREATE TABLE statement:

CREATE TABLE projects(project_id varchar(36) NOT NULL,
project_name varchar(256) NOT NULL,
enforce_members boolean NOT NULL,
tech_start TIMESTAMP(6) NOT NULL DEFAULT CURRENT_TIMESTAMP,
tech_end TIMESTAMP(6) NOT NULL DEFAULT to_timestamp('9999-12-30','YYYY-MM-DD'),
ts_id TIMESTAMP(6) NOT NULL DEFAULT CURRENT_TIMESTAMP, 
PRIMARY KEY(project_id));

ALTER TABLE statement:

alter table projects add constraint fk_projects_containers_11 foreign key (project_id) references containers(container_id) on
delete
    cascade on
    update
    no action ;

Db2

CREATE TABLE statement:

create table projects(project_id varchar(36) not null,
project_name varchar(256) not null,
enforce_members boolean not null,
tech_start TIMESTAMP(12) not null IMPLICITLY HIDDEN generated always as row begin,
tech_end TIMESTAMP(12) not null IMPLICITLY HIDDEN generated always as row
end,
ts_id TIMESTAMP(12) not null generated always as transaction start ID,
primary key(project_id),
period SYSTEM_TIME (tech_start,
tech_end) )

ALTER TABLE statement:

alter table projects add constraint fk_projects_containers_11 foreign key (project_id) references containers(container_id) on
delete
    cascade on
    update
    no action

container_assets table

This table contains information about the assets that are defined in a catalog or project.

This table has the following columns:

  • asset_id - The identifier of the asset.
  • container_id - The identifier of the catalog or project.
  • container_type - Specifies whether the type of the workspace is a catalog or project.
  • name - The name of the asset.
  • description - The description of the asset.
  • owner - The identifier of the user that owns the asset.
  • asset_type - The type of the asset.
  • created_on - The timestamp when the asset was created.
  • modified_on - The timestamp when the asset was last modified.
  • modified_by - The identifier of the user that last modified the asset.
  • rov - The rule of visibility of the asset. For more information, see Asset primary metadata document (or card).
  • asset_state - The current state of the asset, whether available or deleted.
  • source - The information about the source of the asset by providing the source system.
  • source_additional_info - Provides additional information that is related to the source of the asset.
  • resource_key - The unique identifier for an asset that is used for deduplication.
  • asset_category - The asset category, either a user asset or system asset.
  • rating - The average social rating of the asset.
  • total_ratings - The total number of ratings of the asset.
  • format - The format of the data that is associated with the asset, for example CSV, octet-stream, or PDF.
  • origin_country - The country from which the data originated in the format complaint with ISO 3166 Country Codes.
  • size - The size of the local asset.

Postgres

CREATE TABLE statement:

create table container_assets(container_id varchar(36) not null,
container_type varchar(16) not null,
asset_id varchar(128) not null,
name varchar(256) not null,
description text,
asset_type varchar(128) not null,
owner varchar(128) not null,
source text,
source_additional_info text,
resource_key varchar(256),
asset_category varchar(64),
rov integer not null,
asset_state varchar(32) not null,
format varchar(128),
size varchar(36) not null,
created_on timestamp(6) not null,
modified_by varchar(128),
modified_on timestamp(6),
origin_country varchar(128) not null,
rating float,
total_ratings integer,
tech_start TIMESTAMP(6) not null default CURRENT_TIMESTAMP,
tech_end TIMESTAMP(6) not null default to_timestamp('9999-12-30', 'YYYY-MM-DD'),
ts_id TIMESTAMP(6) not null default CURRENT_TIMESTAMP,
primary key(container_id,
asset_id));

ALTER TABLE statement:

alter table container_assets add constraint fk_container_assets_containers_2 foreign key (container_id) references containers(container_id) on
delete
    cascade on
    update
    no action

Db2

CREATE TABLE statement:

create table container_assets(container_id varchar(36) not null,
container_type varchar(16) not null,
asset_id varchar(128) not null,
name varchar(256) not null,
description clob,
asset_type varchar(128) not null,
owner varchar(128) not null,
source clob,
source_additional_info clob,
resource_key varchar(256),
asset_category varchar(64),
rov integer not null,
asset_state varchar(32) not null,
format varchar(128),
size varchar(36) not null,
created_on timestamp(12) not null,
modified_by varchar(128),
modified_on timestamp(12),
origin_country varchar(128) not null,
rating float,
total_ratings integer,
tech_start TIMESTAMP(12) not null IMPLICITLY HIDDEN generated always as row begin,
tech_end TIMESTAMP(12) not null IMPLICITLY HIDDEN generated always as row
end,
ts_id TIMESTAMP(12) not null generated always as transaction start ID,
primary key(container_id,
asset_id),

ALTER TABLE statement:

alter table container_assets add constraint fk_container_assets_containers_2 foreign key (container_id) references containers(container_id) on
delete
    cascade on
    update
    no action

container_data_assets table

This table contains information about the data assets that are defined in a catalog or project.

This table has the following columns:

  • asset_id - The identifier of the asset.
  • container_id - The identifier of the catalog or project.
  • quality_score - The quality score of the asset as determined by profiling.
  • attachments - The additional information that is associated with the data asset. For example, the connection information if some connected assets are present.
  • metadata_import_id - Identifier for the metadata import.
  • metadata_enrichment_id - Identifier for the metadata enrichment.
  • reviewed_on - The assets on reviewed on data.
  • connection_path - The relative connection path.
  • published_to_container_id - The identifier of the target project.
  • source_container_id - Identifier of the source workspace.
  • source_asset_id - Identifier of the source asset.

Postgres

CREATE TABLE statement:

create table container_data_assets(asset_id varchar(128) not null,
container_id varchar(36) not null,
attachments text,
quality_score float,
metadata_enrichment_id varchar(128),
metadata_import_id varchar(128),
reviewed_on timestamp(6),
connection_path varchar(256),
published_to_container_id varchar(36),
source_container_id varchar(36),
source_asset_id varchar(128),
tech_start TIMESTAMP(6) not null default CURRENT_TIMESTAMP,
tech_end TIMESTAMP(6) not null default to_timestamp('9999-12-30', 'YYYY-MM-DD'),
ts_id TIMESTAMP(6) not null default CURRENT_TIMESTAMP,
primary key(container_id,
asset_id))

ALTER TABLE statement:

alter table catalog_data_assets add constraint fk_catalog_data_assets_container_assets_12 foreign key (container_id,
asset_id) references container_assets(container_id,
asset_id) on
delete
    cascade on
    update
    no action

Db2

CREATE TABLE statement:

create table container_data_assets(asset_id varchar(128) not null,
container_id varchar(36) not null,
attachments text,
quality_score float,
metadata_enrichment_id varchar(128),
metadata_import_id varchar(128),
reviewed_on timestamp(6),
connection_path varchar(256),
published_to_container_id varchar(36),
source_container_id varchar(36),
source_asset_id varchar(128),
tech_start TIMESTAMP(6) not null default CURRENT_TIMESTAMP,
tech_end TIMESTAMP(6) not null default to_timestamp('9999-12-30', 'YYYY-MM-DD'),
ts_id TIMESTAMP(6) not null default CURRENT_TIMESTAMP,
primary key(container_id,
asset_id))

ALTER TABLE statement:

alter table catalog_data_assets add constraint fk_catalog_data_assets_container_assets_12 foreign key (container_id,
asset_id) references container_assets(container_id,
asset_id) on
delete
    cascade on
    update
    no action

container_data_asset_columns table

This table contains information about the individual columns in a data asset.

This table has the following columns:

  • asset_id - The identifier of the asset.
  • container_id - The identifier of the catalog or project.
  • name - The name of the column.
  • column_id - The identifier that is associated with the column, when the identifier is available.
  • quality_score - The quality score of the column as determined by profiling.
  • description - The description of the column.
  • reviewed_on - The assets on reviewed on data.

Postgres

CREATE TABLE statement:

create table container_data_asset_columns(asset_id varchar(128) not null,
container_id varchar(36) not null,
column_id varchar(128),
name varchar(256) not null,
description text,
quality_score float,
reviewed_on timestamp(6),
tech_start TIMESTAMP(6) not null default CURRENT_TIMESTAMP,
tech_end TIMESTAMP(6) not null default to_timestamp('9999-12-30', 'YYYY-MM-DD'),
ts_id TIMESTAMP(6) not null default CURRENT_TIMESTAMP,
primary key(container_id,
asset_id,
name))

ALTER TABLE statement:

alter table catalog_data_asset_columns add constraint fk_catalog_data_asset_columns_catalog_data_assets_13 foreign key (container_id,
asset_id) references catalog_data_assets(container_id,
asset_id) on
delete
    cascade on
    update
    no action

Db2

CREATE TABLE statement:

create table container_data_asset_columns(asset_id varchar(128) not null,
container_id varchar(36) not null,
column_id varchar(128),
name varchar(256) not null,
description text,
quality_score float,
reviewed_on timestamp(6),
tech_start TIMESTAMP(6) not null default CURRENT_TIMESTAMP,
tech_end TIMESTAMP(6) not null default to_timestamp('9999-12-30', 'YYYY-MM-DD'),
ts_id TIMESTAMP(6) not null default CURRENT_TIMESTAMP,
primary key(container_id,
asset_id,
name))

ALTER TABLE statement:

alter table catalog_data_asset_columns add constraint fk_catalog_data_asset_columns_catalog_data_assets_13 foreign key (container_id,
asset_id) references catalog_data_assets(container_id,
asset_id) on
delete
    cascade on
    update
    no action

data_asset_column_tags table

This table contains information about the tags that are associated with the columns.

This table has the following columns:

  • column_name - The name of the column.
  • asset_id - The identifier of the data asset.
  • container_id - The identifier of the catalog or project.
  • tagname - The name of the associated tag.

Postgres

CREATE TABLE statement:

create table data_asset_column_tags(asset_id varchar(128) not null,
container_id varchar(36) not null,
tag_name varchar(256) not null,
column_name varchar(256) not null,
tech_start TIMESTAMP(6) not null default CURRENT_TIMESTAMP,
tech_end TIMESTAMP(6) not null default to_timestamp('9999-12-30', 'YYYY-MM-DD'),
ts_id TIMESTAMP(6) not null default CURRENT_TIMESTAMP,
primary key(container_id,
asset_id,
column_name,
tag_name));

ALTER TABLE statements:

alter table data_asset_column_tags add constraint fk_data_asset_column_tags_tags_5 foreign key (tag_name) references tags(tag_name) on
delete
    cascade on
    update
    no action
alter table data_asset_column_tags add constraint fk_data_asset_column_tags_catalog_data_asset_columns_15 foreign key (container_id,
asset_id,
column_name) references catalog_data_asset_columns(container_id,
asset_id,
name) on
delete
    cascade on
    update
    no action

Db2

CREATE TABLE statement:

create table data_asset_column_tags(asset_id varchar(128) not null,
container_id varchar(36) not null,
tag_name varchar(256) not null,
column_name varchar(256) not null,
tech_start TIMESTAMP(12) not null IMPLICITLY HIDDEN generated always as row begin,
tech_end TIMESTAMP(12) not null IMPLICITLY HIDDEN generated always as row
end,
ts_id TIMESTAMP(12) not null generated always as transaction start ID,
primary key(container_id,
asset_id,
column_name,
tag_name),
period SYSTEM_TIME (tech_start,
tech_end) )

ALTER TABLE statements:

alter table data_asset_column_tags add constraint fk_data_asset_column_tags_tags_5 foreign key (tag_name) references tags(tag_name) on
delete
    cascade on
    update
    no action
alter table data_asset_column_tags add constraint fk_data_asset_column_tags_catalog_data_asset_columns_15 foreign key (container_id,
asset_id,
column_name) references catalog_data_asset_columns(container_id,
asset_id,
name) on
delete
    cascade on
    update
    no action

asset_collaborators table

This table contains a list of all the members of an asset.

This table has the following columns:

  • asset_id - The identifier of the asset.
  • container_id - The identifier of the catalog.
  • user_id - The identifier of the collaborator.

Postgres

CREATE TABLE statement:

create table asset_collaborators(asset_id varchar(128) not null,
container_id varchar(36) not null,
user_id varchar(128) not null,
tech_start TIMESTAMP(6) not null default CURRENT_TIMESTAMP,
tech_end TIMESTAMP(6) not null default to_timestamp('9999-12-30', 'YYYY-MM-DD'),
ts_id TIMESTAMP(6) not null default CURRENT_TIMESTAMP,
primary key(container_id,
asset_id,
user_id));

ALTER TABLE statement:

alter table asset_collaborators add constraint fk_asset_collaborators_container_assets_6 foreign key (container_id,
asset_id) references container_assets(container_id,
asset_id) on
delete
    cascade on
    update
    no action

Db2

CREATE TABLE statement:

create table asset_collaborators(asset_id varchar(128) not null,
container_id varchar(36) not null,
user_id varchar(128) not null,
tech_start TIMESTAMP(12) not null IMPLICITLY HIDDEN generated always as row begin,
tech_end TIMESTAMP(12) not null IMPLICITLY HIDDEN generated always as row
end,
ts_id TIMESTAMP(12) not null generated always as transaction start ID,
primary key(container_id,
asset_id,
user_id),
period SYSTEM_TIME (tech_start,
tech_end) )

ALTER TABLE statement:

alter table asset_collaborators add constraint fk_asset_collaborators_container_assets_6 foreign key (container_id,
asset_id) references container_assets(container_id,
asset_id) on
delete
    cascade on
    update
    no action

container_members table

This table contains a list of all members of a catalog or project.

This table has the following columns:

  • container_id - The identifier of the catalog or project.
  • member_id - The identifier of the member or group.
  • is_group - Specifies whether the member is a group. If the value is true, the value of the member_id column is the identifier of the group.
  • role - The roles that are assigned to the user or user group, for example Admin, Editor or Viewer.

Postgres

CREATE TABLE statement:

create table container_members(container_id varchar(36) not null,
is_group boolean not null,
member_id varchar(64) not null,
role varchar(32) not null,
tech_start TIMESTAMP(6) not null default CURRENT_TIMESTAMP,
tech_end TIMESTAMP(6) not null default to_timestamp('9999-12-30', 'YYYY-MM-DD'),
ts_id TIMESTAMP(6) not null default CURRENT_TIMESTAMP,
primary key(container_id,
member_id));

ALTER TABLE statement:

alter table container_members add constraint fk_container_members_containers_1 foreign key (container_id) references containers(container_id) on
delete
    cascade on
    update
    no action

Db2

CREATE TABLE statement:

create table container_members(container_id varchar(36) not null,
is_group boolean not null,
member_id varchar(64) not null,
role varchar(32) not null,
tech_start TIMESTAMP(12) not null IMPLICITLY HIDDEN generated always as row begin,
tech_end TIMESTAMP(12) not null IMPLICITLY HIDDEN generated always as row
end,
ts_id TIMESTAMP(12) not null generated always as transaction start ID,
primary key(container_id,
member_id),
period SYSTEM_TIME (tech_start,
tech_end) )

ALTER TABLE statement:

alter table container_members add constraint fk_container_members_containers_1 foreign key (container_id) references containers(container_id) on
delete
    cascade on
    update
    no action

user_profiles table

This table contains a list of all the users of a catalog or project.

This table has the following columns:

  • user_id - The identifier for the user.
  • user_name - The name of the user.
  • display_name - What name is displayed for the user.
  • first_name - Usrer's first name.
  • last_name - Usrer's last name.
  • email - Usrer's email.

Postgres

CREATE TABLE statement:

CREATE TABLE user_profiles(user_id varchar(128) NOT NULL,user_name varchar(256),display_name varchar(256),first_name varchar(256),last_name varchar(256),email varchar(256),tech_start TIMESTAMP(6) NOT NULL DEFAULT CURRENT_TIMESTAMP,tech_end TIMESTAMP(6) NOT NULL DEFAULT to_timestamp('9999-12-30','YYYY-MM-DD'),ts_id TIMESTAMP(6) NOT NULL DEFAULT CURRENT_TIMESTAMP, PRIMARY KEY(user_id))

Db2

CREATE TABLE statement:

CREATE TABLE user_profiles(user_id varchar(128) NOT NULL,user_name varchar(256),display_name varchar(256),first_name varchar(256),last_name varchar(256),email varchar(256),tech_start TIMESTAMP(12) NOT NULL IMPLICITLY HIDDEN GENERATED ALWAYS AS ROW BEGIN,tech_end TIMESTAMP(12) NOT NULL IMPLICITLY HIDDEN GENERATED ALWAYS AS ROW END,ts_id TIMESTAMP(12) NOT NULL GENERATED ALWAYS AS TRANSACTION START ID, PRIMARY KEY(user_id), PERIOD SYSTEM_TIME (tech_start,tech_end) ) ORGANIZE BY ROW

asset_artifact_relations

This table contains information about the associations between asset and governance artifacts.

The table has the following columns:

  • end1_asset_id - The identifier of the end1 asset.
  • end2_artifact_id - The target artifact ID of the asset-artifact relationship.
  • end1_container_id - The container ID of the end1 asset.
  • end2_artifact_type - The target artifact type of the asset-artifact relationship.
  • end1_relationship_type - The relationship type as identified from the end1 asset.
  • end2_relationship_type - The relationship type as identified from the end2 asset.

Postgres

CREATE TABLE statement:

CREATE TABLE asset_artifact_relations(end1_asset_id varchar(128) NOT NULL,
end1_container_id varchar(36) NOT NULL,
end2_artifact_id varchar(128) NOT NULL,
end2_artifact_type varchar(128) NOT NULL,
end1_relationship_type varchar(256) NOT NULL,
end2_relationship_type varchar(256) NOT NULL,
tech_start TIMESTAMP(6) NOT NULL DEFAULT CURRENT_TIMESTAMP,
tech_end TIMESTAMP(6) NOT NULL DEFAULT to_timestamp('9999-12-30', 'YYYY-MM-DD'),
ts_id TIMESTAMP(6) NOT NULL DEFAULT CURRENT_TIMESTAMP,
PRIMARY KEY(end1_asset_id,
end1_container_id,
end2_artifact_id,
end2_artifact_type,
end1_relationship_type))

ALTER TABLE statements:

alter table asset_artifact_relations add constraint fk_asset_artifact_relations_container_assets_1 foreign key (end1_container_id,
end1_asset_id) references container_assets(container_id,
asset_id) on
delete
    cascade on
    update
    no action
alter table asset_artifact_relations add constraint fk_asset_artifact_relations_governance_artifacts_2 foreign key (end2_artifact_id) references governance_artifacts(artifact_id) on
    delete
    cascade on
    update
    no action

Db2

CREATE TABLE statement:

CREATE TABLE asset_artifact_relations(end1_asset_id varchar(128) NOT NULL,
end1_container_id varchar(36) NOT NULL,
end2_artifact_id varchar(128) NOT NULL,
end2_artifact_type varchar(128) NOT NULL,
end1_relationship_type varchar(256) NOT NULL,
end2_relationship_type varchar(256) NOT NULL,
tech_start TIMESTAMP(12) NOT NULL IMPLICITLY HIDDEN GENERATED ALWAYS AS ROW
BEGIN
    ,
    tech_end TIMESTAMP(12) NOT NULL IMPLICITLY HIDDEN GENERATED ALWAYS AS ROW
END,
ts_id TIMESTAMP(12) NOT NULL GENERATED ALWAYS AS TRANSACTION START ID,
PRIMARY KEY(end1_asset_id,
end1_container_id,
end2_artifact_id,
end2_artifact_type,
end1_relationship_type),
PERIOD SYSTEM_TIME (tech_start,
tech_end) ) ORGANIZE BY ROW

ALTER TABLE statements:

ALTER TABLE asset_artifact_relations ADD CONSTRAINT 
fk_asset_artifact_relations_container_assets_1 FOREIGN KEY (end1_container_id,end1_asset_id)REFERENCES container_assets(container_id,asset_id) ON 
    DELETE
    CASCADE  ON
    UPDATE 
    NO ACTION
ALTER TABLE asset_artifact_relations ADD CONSTRAINT fk_asset_artifact_relations_governance_artifacts_2 FOREIGN KEY (end2_artifact_id) REFERENCES governance_artifacts(artifact_id) ON
DELETE
    CASCADE ON
    UPDATE
    NO ACTION

container_assets_associations table

This table contains information about the relationships between the catalog assets.

This table has the following columns:

  • end1_asset_id - The identifier of the source asset.
  • end2_asset_id - The identifier of the target asset.
  • end1_container_id - The identifier of the workspace of the source asset.
  • end2_container_id - The identifier of the workspace of the target asset.
  • end1_relationship_type - The relationship type as identified from the source asset.
  • end2_relationship_type - The relationship type as identified from the target asset.

Postgres

CREATE TABLE statement:

CREATE TABLE catalog_assets_associations(end1_asset_id varchar(128) NOT NULL,
end2_asset_id varchar(128) NOT NULL,
end1_container_id varchar(36) NOT NULL,
end2_container_id varchar(36) NOT NULL,
end1_relationship_type varchar(128) NOT NULL,
end2_relationship_type varchar(128) NOT NULL,
tech_start TIMESTAMP(6) NOT NULL DEFAULT CURRENT_TIMESTAMP,
tech_end TIMESTAMP(6) NOT NULL DEFAULT to_timestamp('9999-12-30','YYYY-MM-DD'),
ts_id TIMESTAMP(6) NOT NULL DEFAULT CURRENT_TIMESTAMP,
PRIMARY KEY(end1_container_id,
end2_container_id,
end1_asset_id,
end2_asset_id,
end1_relationship_type));

ALTER TABLE statements:

alter table catalog_assets_associations add constraint fk_catalog_assets_associations_container_assets_7 foreign key (end1_container_id,
end1_asset_id) references container_assets(container_id,
asset_id) on
delete
    cascade on
    update
    no action
alter table catalog_assets_associations add constraint fk_catalog_assets_associations_container_assets_8 foreign key (end2_container_id,
end2_asset_id) references container_assets(container_id,
asset_id) on
delete
    cascade on
    update
    no action
alter table catalog_assets_associations add constraint fk_catalog_assets_associations_containers_10 foreign key (end1_container_id) references containers(container_id) on
delete
    cascade on
    update
    no action

Db2

CREATE TABLE statement:

CREATE TABLE catalog_assets_associations(end1_asset_id varchar(128) NOT NULL,
end2_asset_id varchar(128) NOT NULL,
end1_container_id varchar(36) NOT NULL,
end2_container_id varchar(36) NOT NULL,
end1_relationship_type varchar(128) NOT NULL,
end2_relationship_type varchar(128) NOT NULL,
tech_start TIMESTAMP(12) NOT NULL IMPLICITLY HIDDEN GENERATED ALWAYS AS ROW BEGIN,
tech_end TIMESTAMP(12) NOT NULL IMPLICITLY HIDDEN GENERATED ALWAYS AS ROW END,
ts_id TIMESTAMP(12) NOT NULL GENERATED ALWAYS AS TRANSACTION START ID,
PRIMARY KEY(end1_container_id,
end2_container_id,
end1_asset_id,
end2_asset_id,
end1_relationship_type),
PERIOD SYSTEM_TIME (tech_start,
tech_end) )

ALTER TABLE statements:

alter table catalog_assets_associations add constraint fk_catalog_assets_associations_container_assets_7 foreign key (end1_container_id,
end1_asset_id) references container_assets(container_id,
asset_id) on
delete
    cascade on
    update
    no action
alter table catalog_assets_associations add constraint fk_catalog_assets_associations_container_assets_8 foreign key (end2_container_id,
end2_asset_id) references container_assets(container_id,
asset_id) on
delete
    cascade on
    update
    no action
alter table catalog_assets_associations add constraint fk_catalog_assets_associations_containers_10 foreign key (end1_container_id) references containers(container_id) on
delete
    cascade on
    update
    no action

asset_tags table

This table contains information about the tags that are associated with an asset.

This table has the following columns:

  • tag_name - The name of the associated tag.
  • asset_id - The identifier of the asset.
  • container_id - The identifier of the catalog or project.

Postgres

CREATE TABLE statement:

create table asset_tags(asset_id varchar(128) not null,
container_id varchar(36) not null,
tag_name varchar(256) not null,
tech_start TIMESTAMP(6) not null default CURRENT_TIMESTAMP,
tech_end TIMESTAMP(6) not null default to_timestamp('9999-12-30', 'YYYY-MM-DD'),
ts_id TIMESTAMP(6) not null default CURRENT_TIMESTAMP,
primary key(container_id,
asset_id,
tag_name));

ALTER TABLE statements:

alter table asset_tags add constraint fk_asset_tags_container_assets_3 foreign key (container_id,
asset_id) references container_assets(container_id,
asset_id) on
delete
    cascade on
    update
    no action
alter table asset_tags add constraint fk_asset_tags_tags_4 foreign key (tag_name) references tags(tag_name) on
delete
    cascade on
    update
    no action

Db2

CREATE TABLE statement:

create table asset_tags(asset_id varchar(128) not null,
container_id varchar(36) not null,
tag_name varchar(256) not null,
tech_start TIMESTAMP(12) not null IMPLICITLY HIDDEN generated always as row begin,
tech_end TIMESTAMP(12) not null IMPLICITLY HIDDEN generated always as row
end,
ts_id TIMESTAMP(12) not null generated always as transaction start ID,
primary key(container_id,
asset_id,
tag_name),
period SYSTEM_TIME (tech_start,
tech_end) )

ALTER TABLE statements:

alter table asset_tags add constraint fk_asset_tags_container_assets_3 foreign key (container_id,
asset_id) references container_assets(container_id,
asset_id) on
delete
    cascade on
    update
    no action
alter table asset_tags add constraint fk_asset_tags_tags_4 foreign key (tag_name) references tags(tag_name) on
delete
    cascade on
    update
    no action

governance_artifact_container_associations table

This table contains information about governance artifacts, for example business terms or classification, which is associated with a catalog asset.

This table has the following columns:

  • asset_id - The identifier of the asset.
  • container_id - The identifier of the catalog.
  • associated_artifact_id - The identifier of the associated governance artifact.
  • associated_artifact_type - The type of the associated governance artifact, for example glossary_term, classification.
  • system_id - The system identifier or global identifier of the associated governance artifact.
  • assignment_state - The assignment state of the artifact with asset.
  • assignment_date - The assignment date of the artifact with asset.
  • assigned_by - The person who assigned the artifact to an asset.
  • confidence - The confidence on artifact that is assigned to an asset.
  • specification - The algorithm uses to assign artifact.

Postgres

CREATE TABLE statement:

create table governance_artifact_container_associations(asset_id varchar(128) not null,
container_id varchar(36) not null,
associated_artifact_id varchar(128) not null,
associated_artifact_type varchar(128),
system_id varchar(128) not null,
assignment_state varchar(32),
assignment_date timestamp(6),
assigned_by varchar(128),
confidence float,
specification varchar(128),
tech_start TIMESTAMP(6) not null default CURRENT_TIMESTAMP,
tech_end TIMESTAMP(6) not null default to_timestamp('9999-12-30', 'YYYY-MM-DD'),
ts_id TIMESTAMP(6) not null default CURRENT_TIMESTAMP,
primary key(asset_id,
container_id,
associated_artifact_id))

ALTER TABLE statements:

alter table governance_artifact_catalog_associations add constraint fk_governance_artifact_catalog_associations_governance_artifacts_17 foreign key (associated_artifact_id) references governance_artifacts(artifact_id) on
delete
    cascade on
    update
    no action
alter table governance_artifact_catalog_associations add constraint fk_governance_artifact_catalog_associations_container_assets_9 foreign key (container_id,
asset_id) references container_assets(container_id,
asset_id) on
delete
    cascade on
    update
    no action

Db2

CREATE TABLE statement:

create table governance_artifact_container_associations(asset_id varchar(128) not null,
container_id varchar(36) not null,
associated_artifact_id varchar(128) not null,
associated_artifact_type varchar(128),
system_id varchar(128) not null,
assignment_state varchar(32),
assignment_date timestamp(6),
assigned_by varchar(128),
confidence float,
specification varchar(128),
tech_start TIMESTAMP(6) not null default CURRENT_TIMESTAMP,
tech_end TIMESTAMP(6) not null default to_timestamp('9999-12-30', 'YYYY-MM-DD'),
ts_id TIMESTAMP(6) not null default CURRENT_TIMESTAMP,
primary key(asset_id,
container_id,
associated_artifact_id))

ALTER TABLE statements:

alter table governance_artifact_catalog_associations add constraint fk_governance_artifact_catalog_associations_governance_artifacts_17 foreign key (associated_artifact_id) references governance_artifacts(artifact_id) on
delete
    cascade on
    update
    no action
alter table governance_artifact_catalog_associations add constraint fk_governance_artifact_catalog_associations_container_assets_9 foreign key (container_id,
asset_id) references container_assets(container_id,
asset_id) on
delete
    cascade on
    update
    no action

data_asset_column_artifact_associations table

This table contains information about governance artifacts, for example business terms or classifications, which are associated with the column of the data asset.

This table has the following columns:

  • name - The name of the column.
  • asset_id - The identifier of the asset.
  • container_id - The identifier of the catalog.
  • associated_artifact_id - The identifier of the associated governance artifact.
  • associated_artifact_type - The type of the associated governance artifact, for example glossary_term, classification.
  • system_id - The system identifier or global identifier of the associated governance artifact.
  • assignment_state - The assignment state of the artifact with column asset.
  • assignment_date - The assignment date of the artifact with column asset.
  • assigned_by - The person who assigned the artifact to the column asset.
  • confidence - The confidence on artifact that is assigned to an asset.
  • specification - The algorithm uses to assign artifact.

Postgres

CREATE TABLE statement:

create table data_asset_column_artifact_associations(asset_id varchar(128) not null,
container_id varchar(36) not null,
name varchar(256) not null,
associated_artifact_type varchar(128),
associated_artifact_id varchar(128) not null,
system_id varchar(128) not null,
assignment_state varchar(32),
assignment_date timestamp(6),
assigned_by varchar(128),
confidence float,
specification varchar(128),
tech_start TIMESTAMP(6) not null default CURRENT_TIMESTAMP,
tech_end TIMESTAMP(6) not null default to_timestamp('9999-12-30', 'YYYY-MM-DD'),
ts_id TIMESTAMP(6) not null default CURRENT_TIMESTAMP,
primary key(container_id,
asset_id,
name,
associated_artifact_id))

ALTER TABLE statements:

alter table data_asset_column_artifact_associations add constraint fk_data_asset_column_artifact_associations_governance_artifacts_16 foreign key (associated_artifact_id) references governance_artifacts(artifact_id) on
delete
    cascade on
    update
    no action
alter table data_asset_column_artifact_associations add constraint fk_data_asset_column_artifact_associations_catalog_data_asset_columns_14 foreign key (container_id,
asset_id,
name) references catalog_data_asset_columns(container_id,
asset_id,
name) on
delete
    cascade on
    update
    no action

Db2

CREATE TABLE statement:

create table data_asset_column_artifact_associations(asset_id varchar(128) not null,
container_id varchar(36) not null,
name varchar(256) not null,
associated_artifact_type varchar(128),
associated_artifact_id varchar(128) not null,
system_id varchar(128) not null,
assignment_state varchar(32),
assignment_date timestamp(6),
assigned_by varchar(128),
confidence float,
specification varchar(128),
tech_start TIMESTAMP(6) not null default CURRENT_TIMESTAMP,
tech_end TIMESTAMP(6) not null default to_timestamp('9999-12-30', 'YYYY-MM-DD'),
ts_id TIMESTAMP(6) not null default CURRENT_TIMESTAMP,
primary key(container_id,
asset_id,
name,
associated_artifact_id))

ALTER TABLE statements:

alter table data_asset_column_artifact_associations add constraint fk_data_asset_column_artifact_associations_governance_artifacts_16 foreign key (associated_artifact_id) references governance_artifacts(artifact_id) on
delete
    cascade on
    update
    no action
alter table data_asset_column_artifact_associations add constraint fk_data_asset_column_artifact_associations_catalog_data_asset_columns_14 foreign key (container_id,
asset_id,
name) references catalog_data_asset_columns(container_id,
asset_id,
name) on
delete
    cascade on
    update
    no action

Tags table

This table contains a list of tags that are defined.

This table has the following columns:

  • tag_name - The name of the tag.

Postgres

CREATE TABLE statement:

create table tags(tag_name varchar(256) not null,
tech_start TIMESTAMP(6) not null default CURRENT_TIMESTAMP,
tech_end TIMESTAMP(6) not null default to_timestamp('9999-12-30', 'YYYY-MM-DD'),
ts_id TIMESTAMP(6) not null default CURRENT_TIMESTAMP,
primary key(tag_name));

Db2

CREATE TABLE statement:

create table tags(tag_name varchar(256) not null,
tech_start TIMESTAMP(12) not null IMPLICITLY HIDDEN generated always as row begin,
tech_end TIMESTAMP(12) not null IMPLICITLY HIDDEN generated always as row
end,
ts_id TIMESTAMP(12) not null generated always as transaction start ID,
primary key(tag_name),
period SYSTEM_TIME (tech_start,
tech_end) )

enforcement_rules table

This table contains information about the enforcement rules (data protection rules) that are defined.

This table has the following columns:

  • rule_id - The identifier of the rule.
  • rule_type - The type of the rule.
  • name - The name of the rule.
  • created_by - The identifier of the user that created the rule.
  • created_on - The timestamp when the rule was created.
  • modified_by - The identifier of the user that last modified the rule.
  • modified_on - The timestamp when the rule was last modified.
  • description - The description of the rule.
  • action_name - The type of the action that this rule enforces.
  • rule_json - The JSON representation of the defined rule.

Postgres

CREATE TABLE statement:

create table enforcement_rules(rule_id varchar(36) not null,
rule_type varchar(128) not null,
name varchar(256) not null,
description text,
action_name varchar(256) not null,
created_on timestamp(6) not null,
created_by varchar(128) not null,
modified_on timestamp(6),
modified_by varchar(128),
rule_json text not null,
tech_start TIMESTAMP(6) not null default CURRENT_TIMESTAMP,
tech_end TIMESTAMP(6) not null default to_timestamp('9999-12-30', 'YYYY-MM-DD'),
ts_id TIMESTAMP(6) not null default CURRENT_TIMESTAMP,
primary key(rule_id));

Db2

CREATE TABLE statement:

create table enforcement_rules(rule_id varchar(36) not null,
rule_type varchar(128) not null,
name varchar(256) not null,
description clob,
action_name varchar(256) not null,
created_on timestamp(12) not null,
created_by varchar(128) not null,
modified_on timestamp(12),
modified_by varchar(128),
rule_json clob not null,
tech_start TIMESTAMP(12) not null IMPLICITLY HIDDEN generated always as row begin,
tech_end TIMESTAMP(12) not null IMPLICITLY HIDDEN generated always as row
end,
ts_id TIMESTAMP(12) not null generated always as transaction start ID,
primary key(rule_id),
period SYSTEM_TIME (tech_start,
tech_end) )

categories table

This table contains information about the governance categories that are defined.

This table has the following columns:

  • category_id - The identifier of the category.
  • name - The name of the category.
  • description - The description of the category.
  • created_by - The identifier of the user that created the category.
  • created_on - The timestamp when the category was created.
  • modified_by - The identifier of the user that last modified the category.
  • modified_on - The timestamp when the category was last modified.

Postgres

CREATE TABLE statement:

create table categories(category_id varchar(128) not null,
name varchar(256) not null,
description text,
created_by varchar(128) not null,
created_on timestamp(6) not null,
modified_by varchar(128),
modified_on timestamp(6),
tech_start TIMESTAMP(6) not null default CURRENT_TIMESTAMP,
tech_end TIMESTAMP(6) not null default to_timestamp('9999-12-30', 'YYYY-MM-DD'),
ts_id TIMESTAMP(6) not null default CURRENT_TIMESTAMP,
primary key(category_id));

Db2

CREATE TABLE statement:

create table categories(category_id varchar(128) not null,
name varchar(256) not null,
description clob,
created_by varchar(128) not null,
created_on timestamp(12) not null,
modified_by varchar(128),
modified_on timestamp(12),
tech_start TIMESTAMP(12) not null IMPLICITLY HIDDEN generated always as row begin,
tech_end TIMESTAMP(12) not null IMPLICITLY HIDDEN generated always as row
end,
ts_id TIMESTAMP(12) not null generated always as transaction start ID,
primary key(category_id),
period SYSTEM_TIME (tech_start,
tech_end) )

category_collaborators table

This table contains a list of all collaborators of a category.

This table has the following columns:

  • category_id - The identifier of the category.
  • user_id - The identifier of the user.
  • role - The roles that are assigned to this user or user group, for example Owner, Admin, Editor, Reviewer, or Viewer.

Postgres

CREATE TABLE statement:

create table category_collaborators(category_id varchar(128) not null,
user_id varchar(128) not null,
role varchar(128) not null,
user_type varchar(16) not null,
tech_start TIMESTAMP(12) not null default CURRENT_TIMESTAMP,
tech_end TIMESTAMP(12) not null default to_timestamp('9999-12-30', 'YYYY-MM-DD'),
ts_id TIMESTAMP(12) not null default CURRENT_TIMESTAMP,
primary key(category_id,
user_id,
role))

ALTER TABLE statement:

alter table category_collaborators add constraint fk_category_collaborators_categories_20 foreign key (category_id) references categories(category_id) on
delete
    cascade on
    update
    no action

Db2

CREATE TABLE statement:

create table category_collaborators(category_id varchar(128) not null,
user_id varchar(128) not null,
role varchar(128) not null,
user_type varchar(16) not null,
tech_start TIMESTAMP(12) not null IMPLICITLY HIDDEN generated always as row begin,
tech_end TIMESTAMP(12) not null IMPLICITLY HIDDEN generated always as row
end,
ts_id TIMESTAMP(12) not null generated always as transaction start ID,
primary key(category_id,
user_id,
role),
period SYSTEM_TIME (tech_start,
tech_end) ) ORGANIZE by row

ALTER TABLE statement:

alter table category_collaborators add constraint fk_category_collaborators_categories_20 foreign key (category_id) references categories(category_id) on
delete
    cascade on
    update
    no action

category_tags table

This table contains information about the tags that are associated with a category.

This table has the following columns:

  • tag_name - The name of the associated tag.
  • category_id - The identifier of the category.

Postgres

CREATE TABLE statement:

create table category_tags(tag_name varchar(256) not null,
category_id varchar(128) not null,
tech_start TIMESTAMP(6) not null default CURRENT_TIMESTAMP,
tech_end TIMESTAMP(6) not null default to_timestamp('9999-12-30', 'YYYY-MM-DD'),
ts_id TIMESTAMP(6) not null default CURRENT_TIMESTAMP,
primary key(tag_name,
category_id));

ALTER TABLE statements:

alter table category_tags add constraint fk_category_tags_tags_27 foreign key (tag_name) references tags(tag_name) on
delete
    cascade on
    update
    no action
alter table category_tags add constraint fk_category_tags_categories_25 foreign key (category_id) references categories(category_id) on
delete
    cascade on
    update
    no action

Db2

CREATE TABLE statement:

create table category_tags(tag_name varchar(256) not null,
category_id varchar(128) not null,
tech_start TIMESTAMP(12) not null IMPLICITLY HIDDEN generated always as row begin,
tech_end TIMESTAMP(12) not null IMPLICITLY HIDDEN generated always as row
end,
ts_id TIMESTAMP(12) not null generated always as transaction start ID,
primary key(tag_name,
category_id),
period SYSTEM_TIME (tech_start,
tech_end) )

ALTER TABLE statements:

alter table category_tags add constraint fk_category_tags_tags_27 foreign key (tag_name) references tags(tag_name) on
delete
    cascade on
    update
    no action
alter table category_tags add constraint fk_category_tags_categories_25 foreign key (category_id) references categories(category_id) on
delete
    cascade on
    update
    no action

category_associations table

This table contains information about the relationships between categories.

This table has the following columns:

  • end1_category_id - The identifier of the source category.
  • end2_category_id - The identifier of the target category.
  • relationship_type - The relationship type between the two categories, for example parent_category.

Postgres

CREATE TABLE statement:

create table category_associations(end1_category_id varchar(128) not null,
end2_category_id varchar(128) not null,
relationship_type varchar(256) not null,
cr_definition_id varchar(128),
reverse_relationship_type varchar(256),
tech_start TIMESTAMP(6) not null default CURRENT_TIMESTAMP,
tech_end TIMESTAMP(6) not null default to_timestamp('9999-12-30', 'YYYY-MM-DD'),
ts_id TIMESTAMP(6) not null default CURRENT_TIMESTAMP,
primary key(end1_category_id,
end2_category_id,
relationship_type))

ALTER TABLE statement:

alter table category_associations add constraint fk_category_associations_glossary_custom_relationship_def_7 foreign key (cr_definition_id) references glossary_custom_relationship_def(cr_definition_id) on
delete
    cascade on
    update
    no action

Db2

CREATE TABLE statement:

create table category_associations(end1_category_id varchar(128) not null,
end2_category_id varchar(128) not null,
relationship_type varchar(256) not null,
cr_definition_id varchar(128),
reverse_relationship_type varchar(256),
tech_start TIMESTAMP(12) not null IMPLICITLY HIDDEN generated always as row begin,
tech_end TIMESTAMP(12) not null IMPLICITLY HIDDEN generated always as row
end,
ts_id TIMESTAMP(12) not null generated always as transaction start ID,
primary key(end1_category_id,
end2_category_id,
relationship_type),
period SYSTEM_TIME (tech_start,
tech_end) ) ORGANIZE by row

ALTER TABLE statement:

alter table category_associations add constraint fk_category_associations_glossary_custom_relationship_def_7 foreign key (cr_definition_id) references glossary_custom_relationship_def(cr_definition_id) on
delete
    cascade on
    update
    no action

governance_artifacts table

This table contains information about the governance artifacts that are defined in the system that are in the published state.

This table has the following columns:

  • artifact_id - The identifier of the artifact.
  • version_id - The version identifier of the artifact.
  • artifact_type - The type of the artifact, for example glossary_term, classification, data_class, reference_data, rule, or policy.
  • name - The name of the artifact.
  • description - The description of the artifact.
  • created_by - The identifier of the user that created the artifact.
  • created_on - The timestamp when the artifact was created.
  • modified_by - The identifier of the user that last modified the artifact
  • modified_on - The timestamp when the artifact was last modified.
  • primary_category_id - The identifier of the primary category of the artifact.
  • workflow_id - The identifier of the workflow configuration that was used to publish the artifact.
  • effective_start_date - The effective start date that is assigned to the artifact.
  • effective_end_date - The effective end date that is assigned to the artifact.
  • system_id - The system identifier or global identifier of the associated governance artifact.

Postgres

CREATE TABLE statement:

create table governance_artifacts(artifact_id varchar(128) not null,
version_id varchar(128) not null,
artifact_type varchar(128) not null,
name varchar(256) not null,
description text,
created_on timestamp(6) not null,
created_by varchar(128) not null,
modified_on timestamp(6),
modified_by varchar(128),
primary_category_id varchar(128) not null,
effective_start timestamp(6),
effective_end timestamp(6),
system_id varchar(128) default '' not null,
tech_start TIMESTAMP(6) not null default CURRENT_TIMESTAMP,
tech_end TIMESTAMP(6) not null default to_timestamp('9999-12-30', 'YYYY-MM-DD'),
ts_id TIMESTAMP(6) not null default CURRENT_TIMESTAMP,
primary key(artifact_id));

CREATE INDEX statement:

create index idx_governance_artifacts_1 on
governance_artifacts (artifact_type)

ALTER TABLE statement:

alter table governance_artifacts add constraint fk_governance_artifacts_categories_21 foreign key (primary_category_id) references categories(category_id) on
delete
    cascade on
    update
    no action

Db2

CREATE TABLE statement:

create table governance_artifacts(artifact_id varchar(128) not null,
version_id varchar(128) not null,
artifact_type varchar(128) not null,
name varchar(256) not null,
description clob,
created_on timestamp(12) not null,
created_by varchar(128) not null,
modified_on timestamp(12),
modified_by varchar(128),
primary_category_id varchar(128) not null,
effective_start timestamp(12),
effective_end timestamp(12),
system_id varchar(128) default '' not null,
tech_start TIMESTAMP(12) not null IMPLICITLY HIDDEN generated always as row begin,
tech_end TIMESTAMP(12) not null IMPLICITLY HIDDEN generated always as row
end,
ts_id TIMESTAMP(12) not null generated always as transaction start ID,
primary key(artifact_id),
period SYSTEM_TIME (tech_start,
tech_end) )

CREATE INDEX statement:

create index idx_governance_artifacts_1 on
governance_artifacts (artifact_type)

ALTER TABLE statement:

ALTER TABLE governance_artifacts ADD CONSTRAINT fk_governance_artifacts_categories_21 FOREIGN KEY (primary_category_id) REFERENCES categories(category_id) ON DELETE CASCADE  ON UPDATE NO ACTION

governance_artifact_stewards table

This table contains a list of stewards that are assigned to a published artifact.

This table has the following columns:

  • artifact_id - The identifier of the artifact.
  • user_id - The identifier of the user that is assigned as a steward.

Postgres

CREATE TABLE statement:

create table governance_artifact_stewards(artifact_id varchar(128) not null,
user_id varchar(128) not null,
tech_start TIMESTAMP(6) not null default CURRENT_TIMESTAMP,
tech_end TIMESTAMP(6) not null default to_timestamp('9999-12-30', 'YYYY-MM-DD'),
ts_id TIMESTAMP(6) not null default CURRENT_TIMESTAMP,
primary key(artifact_id,
user_id));

ALTER TABLE statement:

alter table governance_artifact_stewards add constraint fk_governance_artifact_stewards_governance_artifacts_3 foreign key (artifact_id) references governance_artifacts(artifact_id) on
delete
    cascade on
    update
    no action

Db2

CREATE TABLE statement:

create table governance_artifact_stewards(artifact_id varchar(128) not null,
user_id varchar(128) not null,
tech_start TIMESTAMP(12) not null IMPLICITLY HIDDEN generated always as row begin,
tech_end TIMESTAMP(12) not null IMPLICITLY HIDDEN generated always as row
end,
ts_id TIMESTAMP(12) not null generated always as transaction start ID,
primary key(artifact_id,
user_id),
period SYSTEM_TIME (tech_start,
tech_end) )

ALTER TABLE statement:

alter table governance_artifact_stewards add constraint fk_governance_artifact_stewards_governance_artifacts_3 foreign key (artifact_id) references governance_artifacts(artifact_id) on
delete
    cascade on
    update
    no action

governance_artifact_associations table

This table contains information about the relationships between the governance artifacts.

This table has the following columns:

  • end1_artifact_id - The identifier of the source artifact.
  • end2_artifact_id - The identifier of the target artifact.
  • end1_artifact_type - The type of the source artifact.
  • end2_artifact_type - The type of the target artifact.
  • relationship_type - The relationship type.

Postgres

CREATE TABLE statement:

create table governance_artifact_associations(end1_artifact_id varchar(128) not null,
end2_artifact_id varchar(128) not null,
relationship_type varchar(256) not null,
end1_artifact_type varchar(128) not null,
end2_artifact_type varchar(128) not null,
cr_definition_id varchar(128),
reverse_relationship_type varchar(256),
tech_start TIMESTAMP(6) not null default CURRENT_TIMESTAMP,
tech_end TIMESTAMP(6) not null default to_timestamp('9999-12-30', 'YYYY-MM-DD'),
ts_id TIMESTAMP(6) not null default CURRENT_TIMESTAMP,
primary key(end1_artifact_id,
end2_artifact_id,
relationship_type))

ALTER TABLE statement:

alter table governance_artifact_associations add constraint fk_governance_artifact_associations_glossary_custom_relationship_def_8 foreign key (cr_definition_id) references glossary_custom_relationship_def(cr_definition_id) on
delete
    cascade on
    update
    no action

Db2

CREATE TABLE statement:

create table governance_artifact_associations(end1_artifact_id varchar(128) not null,
end2_artifact_id varchar(128) not null,
relationship_type varchar(256) not null,
end1_artifact_type varchar(128) not null,
end2_artifact_type varchar(128) not null,
cr_definition_id varchar(128),
reverse_relationship_type varchar(256),
tech_start TIMESTAMP(12) not null IMPLICITLY HIDDEN generated always as row begin,
tech_end TIMESTAMP(12) not null IMPLICITLY HIDDEN generated always as row
end,
ts_id TIMESTAMP(12) not null generated always as transaction start ID,
primary key(end1_artifact_id,
end2_artifact_id,
relationship_type),
period SYSTEM_TIME (tech_start,
tech_end) ) ORGANIZE by row

ALTER TABLE statement:

alter table governance_artifact_associations add constraint fk_governance_artifact_associations_glossary_custom_relationship_def_8 foreign key (cr_definition_id) references glossary_custom_relationship_def(cr_definition_id) on
delete
    cascade on
    update
    no action

artifact_tags table

This table contains information about the tags that are associated with an artifact.

This table has the following columns:

  • tag_name - The name of the associated tag.
  • artifact_id - The identifier of the artifact.
  • artifact_type - The type of the artifact, for example glossary_term, classification, data_class, reference_data, rule, or policy.

Postgres

CREATE TABLE statement:

create table artifact_tags(tag_name varchar(256) not null,
artifact_id varchar(128) not null,
artifact_type varchar(128) not null,
tech_start TIMESTAMP(6) not null default CURRENT_TIMESTAMP,
tech_end TIMESTAMP(6) not null default to_timestamp('9999-12-30', 'YYYY-MM-DD'),
ts_id TIMESTAMP(6) not null default CURRENT_TIMESTAMP,
primary key(tag_name,
artifact_id));

ALTER TABLE statements:

alter table artifact_tags add constraint fk_artifact_tags_governance_artifacts_24 foreign key (artifact_id) references governance_artifacts(artifact_id) on
delete
    cascade on
    update
    no action
alter table artifact_tags add constraint fk_artifact_tags_tags_26 foreign key (tag_name) references tags(tag_name) on
delete
    cascade on
    update
    no action

Db2

CREATE TABLE statement:

create table artifact_tags(tag_name varchar(256) not null,
artifact_id varchar(128) not null,
artifact_type varchar(128) not null,
tech_start TIMESTAMP(12) not null IMPLICITLY HIDDEN generated always as row begin,
tech_end TIMESTAMP(12) not null IMPLICITLY HIDDEN generated always as row
end,
ts_id TIMESTAMP(12) not null generated always as transaction start ID,
primary key(tag_name,
artifact_id),
period SYSTEM_TIME (tech_start,
tech_end) )

ALTER TABLE statements:

alter table artifact_tags add constraint fk_artifact_tags_governance_artifacts_24 foreign key (artifact_id) references governance_artifacts(artifact_id) on
delete
    cascade on
    update
    no action
alter table artifact_tags add constraint fk_artifact_tags_tags_26 foreign key (tag_name) references tags(tag_name) on
delete
    cascade on
    update
    no action

secondary_category_associations table

This table contains a list of secondary categories to which an artifact is assigned.

This table has the following columns:

  • artifact_id - The identifier of the artifact.
  • category_id - The identifier of the secondary category of the specified artifact.

Postgres

CREATE TABLE statement:

create table secondary_category_associations(category_id varchar(128) not null,
artifact_id varchar(128) not null,
tech_start TIMESTAMP(6) not null default CURRENT_TIMESTAMP,
tech_end TIMESTAMP(6) not null default to_timestamp('9999-12-30', 'YYYY-MM-DD'),
ts_id TIMESTAMP(6) not null default CURRENT_TIMESTAMP,
primary key(category_id,
artifact_id));

ALTER TABLE statements:

alter table secondary_category_associations add constraint fk_secondary_category_associations_categories_22 foreign key (category_id) references categories(category_id) on
delete
    cascade on
    update
    no action
alter table secondary_category_associations add constraint fk_secondary_category_associations_governance_artifacts_23 foreign key (artifact_id) references governance_artifacts(artifact_id) on
delete
    cascade on
    update
    no action

Db2

CREATE TABLE statement:

create table secondary_category_associations(category_id varchar(128) not null,
artifact_id varchar(128) not null,
tech_start TIMESTAMP(12) not null IMPLICITLY HIDDEN generated always as row begin,
tech_end TIMESTAMP(12) not null IMPLICITLY HIDDEN generated always as row
end,
ts_id TIMESTAMP(12) not null generated always as transaction start ID,
primary key(category_id,
artifact_id),
period SYSTEM_TIME (tech_start,
tech_end) )

ALTER TABLE statements:

alter table secondary_category_associations add constraint fk_secondary_category_associations_categories_22 foreign key (category_id) references categories(category_id) on
delete
    cascade on
    update
    no action
alter table secondary_category_associations add constraint fk_secondary_category_associations_governance_artifacts_23 foreign key (artifact_id) references governance_artifacts(artifact_id) on
delete
    cascade on
    update
    no action

business_term_associations table

This table contains information about the relationships between business terms.

This table has the following columns:

  • end1_term_artifact_id - The identifier of the source artifact.
  • end2_term_artifact_id - The identifier of the target artifact.
  • relationship_type - The type of the relationship as identified from the source artifact to the target artifact.
  • reverse_relationship_type - The type of the relationship as identified from the target artifact to the source artifact.

Postgres

CREATE TABLE statement:

create table business_term_associations(end1_artifact_id varchar(128) not null,
end2_artifact_id varchar(128) not null,
relationship_type varchar(256) not null,
reverse_relationship_type varchar(128),
cr_definition_id varchar(128),
tech_start TIMESTAMP(6) not null default CURRENT_TIMESTAMP,
tech_end TIMESTAMP(6) not null default to_timestamp('9999-12-30', 'YYYY-MM-DD'),
ts_id TIMESTAMP(6) not null default CURRENT_TIMESTAMP,
primary key(end1_artifact_id,
end2_artifact_id,
relationship_type))

ALTER TABLE statement:

alter table business_term_associations add constraint fk_business_term_associations_glossary_custom_relationship_def_1 foreign key (cr_definition_id) references glossary_custom_relationship_def(cr_definition_id) on
delete
    cascade on
    update
    no action

Db2

CREATE TABLE statement:

create table business_term_associations(end1_artifact_id varchar(128) not null,
end2_artifact_id varchar(128) not null,
relationship_type varchar(256) not null,
reverse_relationship_type varchar(128),
cr_definition_id varchar(128),
tech_start TIMESTAMP(12) not null IMPLICITLY HIDDEN generated always as row begin,
tech_end TIMESTAMP(12) not null IMPLICITLY HIDDEN generated always as row
end,
ts_id TIMESTAMP(12) not null generated always as transaction start ID,
primary key(end1_artifact_id,
end2_artifact_id,
relationship_type),
period SYSTEM_TIME (tech_start,
tech_end) ) ORGANIZE by row

ALTER TABLE statement:

alter table business_term_associations add constraint fk_business_term_associations_glossary_custom_relationship_def_1 foreign key (cr_definition_id) references glossary_custom_relationship_def(cr_definition_id) on
delete
    cascade on
    update
    no action

data_class_associations table

This table contains information about the relationships between data classes.

This table has the following columns:

  • end1_data_class_artifact_id - The identifier of the source artifact.
  • end2_data_class_artifact_id - The identifier of the target artifact.
  • relationship_type - The type of the relationship as identified from the source artifact to the target artifact.
  • reverse_relationship_type - The type of the relationship as identified from the target artifact to the source artifact.

Postgres

CREATE TABLE statement:

create table data_class_associations(end1_artifact_id varchar(128) not null,
end2_artifact_id varchar(128) not null,
relationship_type varchar(256) not null,
reverse_relationship_type varchar(128),
cr_definition_id varchar(128),
tech_start TIMESTAMP(6) not null default CURRENT_TIMESTAMP,
tech_end TIMESTAMP(6) not null default to_timestamp('9999-12-30', 'YYYY-MM-DD'),
ts_id TIMESTAMP(6) not null default CURRENT_TIMESTAMP,
primary key(end1_artifact_id,
end2_artifact_id,
relationship_type))

ALTER TABLE statement:

alter table data_class_associations add constraint fk_data_class_associations_glossary_custom_relationship_def_3 foreign key (cr_definition_id) references glossary_custom_relationship_def(cr_definition_id) on
delete
    cascade on
    update
    no action

Db2

CREATE TABLE statement:

create table data_class_associations(end1_artifact_id varchar(128) not null,
end2_artifact_id varchar(128) not null,
relationship_type varchar(256) not null,
reverse_relationship_type varchar(128),
cr_definition_id varchar(128),
tech_start TIMESTAMP(12) not null IMPLICITLY HIDDEN generated always as row begin,
tech_end TIMESTAMP(12) not null IMPLICITLY HIDDEN generated always as row
end,
ts_id TIMESTAMP(12) not null generated always as transaction start ID,
primary key(end1_artifact_id,
end2_artifact_id,
relationship_type),
period SYSTEM_TIME (tech_start,
tech_end) ) ORGANIZE by row

ALTER TABLE statement:

alter table data_class_associations add constraint fk_data_class_associations_glossary_custom_relationship_def_3 foreign key (cr_definition_id) references glossary_custom_relationship_def(cr_definition_id) on
delete
    cascade on
    update
    no action

policy_associations

This table contains information about the relationships between policies.

This table has the following columns:

  • end1_policy_artifact_id - The identifier of the source artifact.
  • end2_policy_artifact_id - The identifier of the target artifact.
  • relationship_type - The type of the relationship as identified from the source artifact to the target artifact.
  • reverse_relationship_type - The type of the relationship as identified from the target artifact to the source artifact.

Postgres

CREATE TABLE statement:

create table policy_associations(end1_artifact_id varchar(128) not null,
end2_artifact_id varchar(128) not null,
relationship_type varchar(256) not null,
reverse_relationship_type varchar(128),
cr_definition_id varchar(128),
tech_start TIMESTAMP(6) not null default CURRENT_TIMESTAMP,
tech_end TIMESTAMP(6) not null default to_timestamp('9999-12-30', 'YYYY-MM-DD'),
ts_id TIMESTAMP(6) not null default CURRENT_TIMESTAMP,
primary key(end1_artifact_id,
end2_artifact_id,
relationship_type))

ALTER TABLE statements:

alter table policy_associations add constraint fk_policy_associations_glossary_custom_relationship_def_4 foreign key (cr_definition_id) references glossary_custom_relationship_def(cr_definition_id) on
delete
    cascade on
    update
    no action

Db2

CREATE TABLE statement:

create table policy_associations(end1_artifact_id varchar(128) not null,
end2_artifact_id varchar(128) not null,
relationship_type varchar(256) not null,
reverse_relationship_type varchar(128),
cr_definition_id varchar(128),
tech_start TIMESTAMP(12) not null IMPLICITLY HIDDEN generated always as row begin,
tech_end TIMESTAMP(12) not null IMPLICITLY HIDDEN generated always as row
end,
ts_id TIMESTAMP(12) not null generated always as transaction start ID,
primary key(end1_artifact_id,
end2_artifact_id,
relationship_type),
period SYSTEM_TIME (tech_start,
tech_end) ) ORGANIZE by row

ALTER TABLE statement:

alter table policy_associations add constraint fk_policy_associations_glossary_custom_relationship_def_4 foreign key (cr_definition_id) references glossary_custom_relationship_def(cr_definition_id) on
delete
    cascade on
    update
    no action

reference_data_set_associations table

This table contains information about the relationships between reference data sets.

This table has the following columns:

  • end1_rds_artifact_id - The identifier of the source artifact.
  • end2_rds_artifact_id - The identifier of the target artifact.
  • relationship_type - The type of the relationship as identified from the source artifact to the target artifact.
  • reverse_relationship_type - The type of the relationship as identified from the target artifact to the source artifact.

Postgres

CREATE TABLE statement:

create table reference_data_set_associations(end1_artifact_id varchar(128) not null,
end2_artifact_id varchar(128) not null,
relationship_type varchar(256) not null,
reverse_relationship_type varchar(128),
cr_definition_id varchar(128),
tech_start TIMESTAMP(6) not null default CURRENT_TIMESTAMP,
tech_end TIMESTAMP(6) not null default to_timestamp('9999-12-30', 'YYYY-MM-DD'),
ts_id TIMESTAMP(6) not null default CURRENT_TIMESTAMP,
primary key(end1_artifact_id,
end2_artifact_id,
relationship_type))

ALTER TABLE statement:

ALTER TABLE reference_data_set_associations ADD CONSTRAINT fk_reference_data_set_associations_glossary_custom_relationship_def_5 FOREIGN KEY (cr_definition_id) REFERENCES glossary_custom_relationship_def(cr_definition_id) ON
delete
    cascade on
    update
    no action

Db2

CREATE TABLE statement:

create table reference_data_set_associations(end1_artifact_id varchar(128) not null,
end2_artifact_id varchar(128) not null,
relationship_type varchar(256) not null,
reverse_relationship_type varchar(128),
cr_definition_id varchar(128),
tech_start TIMESTAMP(12) not null IMPLICITLY HIDDEN generated always as row begin,
tech_end TIMESTAMP(12) not null IMPLICITLY HIDDEN generated always as row
end,
ts_id TIMESTAMP(12) not null generated always as transaction start ID,
primary key(end1_artifact_id,
end2_artifact_id,
relationship_type),
period SYSTEM_TIME (tech_start,
tech_end) ) ORGANIZE by row

ALTER TABLE statement:

alter table reference_data_set_associations add constraint fk_reference_data_set_associations_glossary_custom_relationship_def_5 foreign key (cr_definition_id) references glossary_custom_relationship_def(cr_definition_id) on
delete
    cascade on
    update
    no action

classification_associations table

This table contains information about the relationships between classifications.

This table has the following columns:

  • end1_classifiaction_artifact_id - The identifier of the source artifact.
  • end2_classifiaction_artifact_id - The identifier of the target artifact.
  • relationship_type - The type of the relationship as identified from the source artifact to the target artifact.
  • reverse_relationship_type - The type of the relationship as identified from the target artifact to the source artifact.

Postgres

CREATE TABLE statement:

create table classification_associations(end1_artifact_id varchar(128) not null,
end2_artifact_id varchar(128) not null,
relationship_type varchar(256) not null,
reverse_relationship_type varchar(128),
cr_definition_id varchar(128),
tech_start TIMESTAMP(6) not null default CURRENT_TIMESTAMP,
tech_end TIMESTAMP(6) not null default to_timestamp('9999-12-30', 'YYYY-MM-DD'),
ts_id TIMESTAMP(6) not null default CURRENT_TIMESTAMP,
primary key(end1_artifact_id,
end2_artifact_id,
relationship_type))

ALTER TABLE statement:

alter table classification_associations add constraint fk_classification_associations_glossary_custom_relationship_def_2 foreign key (cr_definition_id) references glossary_custom_relationship_def(cr_definition_id) on
delete
    cascade on
    update
    no action

Db2

CREATE TABLE statement:

create table classification_associations(end1_artifact_id varchar(128) not null,
end2_artifact_id varchar(128) not null,
relationship_type varchar(256) not null,
reverse_relationship_type varchar(128),
cr_definition_id varchar(128),
tech_start TIMESTAMP(12) not null IMPLICITLY HIDDEN generated always as row begin,
tech_end TIMESTAMP(12) not null IMPLICITLY HIDDEN generated always as row
end,
ts_id TIMESTAMP(12) not null generated always as transaction start ID,
primary key(end1_artifact_id,
end2_artifact_id,
relationship_type),
period SYSTEM_TIME (tech_start,
tech_end) ) ORGANIZE by row

ALTER TABLE statement:

alter table classification_associations add constraint fk_classification_associations_glossary_custom_relationship_def_2 foreign key (cr_definition_id) references glossary_custom_relationship_def(cr_definition_id) on
delete
    cascade on
    update
    no action

governance_rule_associations table

This table contains information about the relationships between governance rules.

This table has the following columns:

  • end1_rule_artifact_id - The identifier of the source artifact.
  • end2_rule_artifact_id - The identifier of the target artifact.
  • relationship_type - The type of the relationship as identified from the source artifact to the target artifact.
  • reverse_relationship_type - The type of the relationship as identified from the target artifact to the source artifact.

Postgres

CREATE TABLE statement:

create table governance_rule_associations(end1_artifact_id varchar(128) not null,
end2_artifact_id varchar(128) not null,
relationship_type varchar(256) not null,
reverse_relationship_type varchar(128),
cr_definition_id varchar(128),
tech_start TIMESTAMP(6) not null default CURRENT_TIMESTAMP,
tech_end TIMESTAMP(6) not null default to_timestamp('9999-12-30', 'YYYY-MM-DD'),
ts_id TIMESTAMP(6) not null default CURRENT_TIMESTAMP,
primary key(end1_artifact_id,
end2_artifact_id,
relationship_type))

ALTER TABLE statement:

alter table governance_rule_associations add constraint fk_governance_rule_associations_glossary_custom_relationship_def_6 foreign key (cr_definition_id) references glossary_custom_relationship_def(cr_definition_id) on
delete
    cascade on
    update
    no action

Db2

CREATE TABLE statement:

create table governance_rule_associations(end1_artifact_id varchar(128) not null,
end2_artifact_id varchar(128) not null,
relationship_type varchar(256) not null,
reverse_relationship_type varchar(128),
cr_definition_id varchar(128),
tech_start TIMESTAMP(12) not null IMPLICITLY HIDDEN generated always as row begin,
tech_end TIMESTAMP(12) not null IMPLICITLY HIDDEN generated always as row
end,
ts_id TIMESTAMP(12) not null generated always as transaction start ID,
primary key(end1_artifact_id,
end2_artifact_id,
relationship_type),
period SYSTEM_TIME (tech_start,
tech_end) ) ORGANIZE by row

ALTER TABLE statement:

alter table governance_rule_associations add constraint fk_governance_rule_associations_glossary_custom_relationship_def_6 foreign key (cr_definition_id) references glossary_custom_relationship_def(cr_definition_id) on
delete
    cascade on
    update
    no action

artifact_enforcement_rule_associations table

This table contains information about the implicit relationships between a governance artifact and enforcement rules.

This table has the following columns:

  • artifact_id - The identifier of the associated governance artifact.
  • rule_id - The identifier of the enforcement rule that the associated artifact is a part of.

Postgres

CREATE TABLE statement:

create table artifact_enforcement_rule_associations(artifact_id varchar(128) not null,
rule_id varchar(128) not null,
tech_start TIMESTAMP(6) not null default CURRENT_TIMESTAMP,
tech_end TIMESTAMP(6) not null default to_timestamp('9999-12-30', 'YYYY-MM-DD'),
ts_id TIMESTAMP(6) not null default CURRENT_TIMESTAMP,
primary key(artifact_id,
rule_id));

ALTER TABLE statements:

alter table artifact_enforcement_rule_associations add constraint fk_artifact_enforcement_rule_associations_governance_artifacts_18 foreign key (artifact_id) references governance_artifacts(artifact_id) on
delete
    cascade on
    update
    no action
alter table artifact_enforcement_rule_associations add constraint fk_artifact_enforcement_rule_associations_enforcement_rules_19 foreign key (rule_id) references enforcement_rules(rule_id) on
delete
    cascade on
    update
    no action

Db2

CREATE TABLE statement:

create table artifact_enforcement_rule_associations(artifact_id varchar(128) not null,
rule_id varchar(128) not null,
tech_start TIMESTAMP(12) not null IMPLICITLY HIDDEN generated always as row begin,
tech_end TIMESTAMP(12) not null IMPLICITLY HIDDEN generated always as row
end,
ts_id TIMESTAMP(12) not null generated always as transaction start ID,
primary key(artifact_id,
rule_id),
period SYSTEM_TIME (tech_start,
tech_end) )

ALTER TABLE statements:

alter table artifact_enforcement_rule_associations add constraint fk_artifact_enforcement_rule_associations_governance_artifacts_18 foreign key (artifact_id) references governance_artifacts(artifact_id) on
delete
    cascade on
    update
    no action
alter table artifact_enforcement_rule_associations add constraint fk_artifact_enforcement_rule_associations_enforcement_rules_19 foreign key (rule_id) references enforcement_rules(rule_id) on
delete
    cascade on
    update
    no action

asset_quality_score_problems table

This table contains information about the quality problems for the data asset.

This table has the following columns:

  • asset_id - The identifier of the asset.
  • container_id - The identifier of the project.
  • problem_id - The identifier of the problem.
  • num_of_findings : The number of data quality problems of the asset as determined by profiling.
  • percentage - The percentage of data quality problems of the asset as determined by profiling.

Postgres

CREATE TABLE statement:

create table asset_quality_score_problems(asset_id varchar(128) not null,
container_id varchar(36) not null,
problem_id varchar(128) not null,
num_of_findings float not null,
percentage float not null,
tech_start TIMESTAMP(6) not null default CURRENT_TIMESTAMP,
tech_end TIMESTAMP(6) not null default to_timestamp('9999-12-30', 'YYYY-MM-DD'),
ts_id TIMESTAMP(6) not null default CURRENT_TIMESTAMP,
primary key(asset_id,
container_id,
problem_id))

ALTER TABLE statements:

alter table asset_quality_score_problems add constraint fk_asset_quality_score_problems_container_data_assets_1 foreign key (container_id,
asset_id) references container_data_assets(container_id,
asset_id) on
delete
    cascade on
    update
    no action
alter table asset_quality_score_problems add constraint fk_asset_quality_score_problems_dq_problems_3 foreign key (problem_id) references dq_problems(problem_id) on
delete
    cascade on
    update
    no action

Db2

CREATE TABLE statement:

create table asset_quality_score_problems(asset_id varchar(128) not null,
container_id varchar(36) not null,
problem_id varchar(128) not null,
num_of_findings float not null,
percentage float not null,
tech_start TIMESTAMP(12) not null IMPLICITLY HIDDEN generated always as row begin,
tech_end TIMESTAMP(12) not null IMPLICITLY HIDDEN generated always as row
end,
ts_id TIMESTAMP(12) not null generated always as transaction start ID,
primary key(asset_id,
container_id,
problem_id),
period SYSTEM_TIME (tech_start,
tech_end) ) ORGANIZE by row

ALTER TABLE statements:

alter table asset_quality_score_problems add constraint fk_asset_quality_score_problems_container_data_assets_1 foreign key (container_id,
asset_id) references container_data_assets(container_id,
asset_id) on
delete
    cascade on
    update
    no action
alter table asset_quality_score_problems add constraint fk_asset_quality_score_problems_dq_problems_3 foreign key (problem_id) references dq_problems(problem_id) on
delete
    cascade on
    update
    no action

asset_columns_quality_score_problems table

This table contains information about the quality problems for the data asset column.

This table has the following columns:

  • asset_id - The identifier of the asset.
  • container_id - The identifier of the project.
  • column_name - The name of the column.
  • problem_id - The identifier of the problem.
  • num_of_findings - The number of data quality problems of the column as determined by profiling.
  • percentage - The percentage of data quality problems of the column as determined by profiling.

Postgres

CREATE TABLE statement:

create table asset_columns_quality_score_problems(asset_id varchar(128) not null,
container_id varchar(36) not null,
column_name varchar(256) not null,
problem_id varchar(128) not null,
num_of_findings float not null,
percentage float not null,
tech_start TIMESTAMP(12) not null IMPLICITLY HIDDEN generated always as row begin,
tech_end TIMESTAMP(12) not null IMPLICITLY HIDDEN generated always as row
end,
ts_id TIMESTAMP(12) not null generated always as transaction start ID,
primary key(asset_id,
container_id,
column_name,
problem_id),
period SYSTEM_TIME (tech_start,
tech_end) ) ORGANIZE by row

ALTER TABLE statements:

alter table asset_columns_quality_score_problems add constraint fk_asset_columns_quality_score_problems_container_data_asset_columns_2 foreign key (container_id,
asset_id,
column_name) references container_data_asset_columns(container_id,
asset_id,
name) on
delete
    cascade on
    update
    no action
alter table asset_columns_quality_score_problems add constraint fk_asset_columns_quality_score_problems_dq_problems_4 foreign key (problem_id) references dq_problems(problem_id) on
delete
    cascade on
    update
    no action

Db2

CREATE TABLE statement:

create table asset_columns_quality_score_problems(asset_id varchar(128) not null,
container_id varchar(36) not null,
column_name varchar(256) not null,
problem_id varchar(128) not null,
num_of_findings float not null,
percentage float not null,
tech_start TIMESTAMP(12) not null IMPLICITLY HIDDEN generated always as row begin,
tech_end TIMESTAMP(12) not null IMPLICITLY HIDDEN generated always as row
end,
ts_id TIMESTAMP(12) not null generated always as transaction start ID,
primary key(asset_id,
container_id,
column_name,
problem_id),
period SYSTEM_TIME (tech_start,
tech_end) ) ORGANIZE by row

ALTER TABLE statements:

alter table asset_columns_quality_score_problems add constraint fk_asset_columns_quality_score_problems_container_data_asset_columns_2 foreign key (container_id,
asset_id,
column_name) references container_data_asset_columns(container_id,
asset_id,
name) on
delete
    cascade on
    update
    no action
alter table asset_columns_quality_score_problems add constraint fk_asset_columns_quality_score_problems_dq_problems_4 foreign key (problem_id) references dq_problems(problem_id) on
delete
    cascade on
    update
    no action

metadata_imports table

This table contains information about the metadata import.

This table has the following columns:

  • metadata_import_id - Identifier for the metadata import.
  • container_id - The identifier of the project.
  • metadata_import_name - The name of the metadata import.
  • target_container_id - The identifier of the target project.
  • connection_id - The connection identifier on which an import is created.

Postgres

CREATE TABLE statement:

create table metadata_imports(metadata_import_id varchar(128) not null,
container_id varchar(128) not null,
metadata_import_name varchar(256) not null,
target_container_id varchar(128),
connection_id varchar(128),
metadata_enrichment_id varchar(128),
tech_start TIMESTAMP(6) not null default CURRENT_TIMESTAMP,
tech_end TIMESTAMP(6) not null default to_timestamp('9999-12-30', 'YYYY-MM-DD'),
ts_id TIMESTAMP(6) not null default CURRENT_TIMESTAMP,
primary key(container_id,
metadata_import_id))

ALTER TABLE statement:

alter table metadata_imports add constraint fk_metadata_imports_container_assets_2 foreign key (container_id,
metadata_import_id) references container_assets(container_id,
asset_id) on
delete
    cascade on
    update
    no action

Db2

CREATE TABLE statement:

create table metadata_imports(metadata_import_id varchar(128) not null,
container_id varchar(128) not null,
metadata_import_name varchar(256) not null,
target_container_id varchar(128),
connection_id varchar(128),
metadata_enrichment_id varchar(128),
tech_start TIMESTAMP(12) not null IMPLICITLY HIDDEN generated always as row begin,
tech_end TIMESTAMP(12) not null IMPLICITLY HIDDEN generated always as row
end,
ts_id TIMESTAMP(12) not null generated always as transaction start ID,
primary key(container_id,
metadata_import_id),
period SYSTEM_TIME (tech_start,
tech_end) ) ORGANIZE by row

ALTER TABLE statement:

alter table metadata_imports add constraint fk_metadata_imports_container_assets_2 foreign key (container_id,
metadata_import_id) references container_assets(container_id,
asset_id) on
delete
    cascade on
    update
    no action

metadata_import_executions table

This table contains information about the Metadata Import job.

This table has the following columns:

  • metadata_import_id - Identifier for the metadata import.
  • container_id - The identifier of the project.
  • job_run_id - The identifier of the job run.
  • invoked_by - The ID of the person who started it.
  • is_scheduled_run - The scheduled time of the job for metadata import job.
  • start_time - The start time of the job for metadata import job.
  • end_time - The end time of the job for metadata import job.
  • state - The state of the metadata import job.
  • count_discovered - The number of assets that is discovered.
  • count_discovered_with_children - The number of assets with children that is discovered.
  • count_submitted - The number of assets that is discovered.
  • count_succeeded - The number of assets that is imported successfully.
  • count_succedded_with_children - The number of assets with children that is imported successfully.
  • count_new_assets - The number of new assets.
  • count_updated_assets - The number of updated assets.
  • count_deleted_assets - The number of deleted assets.

Postgres

CREATE TABLE statement:

create table metadata_import_executions(metadata_import_id varchar(128) not null,
container_id varchar(36) not null,
job_run_id varchar(128) not null,
invoked_by varchar(128) not null,
is_scheduled_run boolean not null,
start_time timestamp(6) not null,
end_time timestamp(6),
state varchar(32) not null,
count_discovered bigint default 0 not null,
count_discovered_with_children bigint default 0 not null,
count_submitted bigint default 0 not null,
count_succeeded bigint default 0 not null,
count_succedded_with_children bigint default 0 not null,
count_new_assets bigint default 0 not null,
count_updated_assets bigint default 0 not null,
count_deleted_assets bigint default 0 not null,
tech_start TIMESTAMP(6) not null default CURRENT_TIMESTAMP,
tech_end TIMESTAMP(6) not null default to_timestamp('9999-12-30', 'YYYY-MM-DD'),
ts_id TIMESTAMP(6) not null default CURRENT_TIMESTAMP,
primary key(container_id,
metadata_import_id,
job_run_id))

ALTER TABLE statements:

alter table metadata_import_executions add constraint fk_metadata_import_executions_metadata_imports_3 foreign key (container_id,
metadata_import_id) references metadata_imports(container_id,
metadata_import_id) on
delete
    cascade on
    update
    no action
alter table metadata_import_executions add constraint fk_metadata_import_executions_container_assets_4 foreign key (container_id,
job_run_id) references container_assets(container_id,
asset_id) on
delete
    cascade on
    update
    no action

Db2

CREATE TABLE statement:

create table metadata_import_executions(metadata_import_id varchar(128) not null,
container_id varchar(36) not null,
job_run_id varchar(128) not null,
invoked_by varchar(128) not null,
is_scheduled_run boolean not null,
start_time timestamp(12) not null,
end_time timestamp(12),
state varchar(32) not null,
count_discovered bigint default 0 not null,
count_discovered_with_children bigint default 0 not null,
count_submitted bigint default 0 not null,
count_succeeded bigint default 0 not null,
count_succedded_with_children bigint default 0 not null,
count_new_assets bigint default 0 not null,
count_updated_assets bigint default 0 not null,
count_deleted_assets bigint default 0 not null,
tech_start TIMESTAMP(12) not null IMPLICITLY HIDDEN generated always as row begin,
tech_end TIMESTAMP(12) not null IMPLICITLY HIDDEN generated always as row
end,
ts_id TIMESTAMP(12) not null generated always as transaction start ID,
primary key(container_id,
metadata_import_id,
job_run_id),
period SYSTEM_TIME (tech_start,
tech_end) ) ORGANIZE by row

ALTER TABLE statements:

alter table metadata_import_executions add constraint fk_metadata_import_executions_metadata_imports_3 foreign key (container_id,
metadata_import_id) references metadata_imports(container_id,
metadata_import_id) on
delete
    cascade on
    update
    no action
alter table metadata_import_executions add constraint fk_metadata_import_executions_container_assets_4 foreign key (container_id,
job_run_id) references container_assets(container_id,
asset_id) on
delete
    cascade on
    update
    no action

metadata_enrichments table

This table contains information about the metadata enrichments.

This table has the following columns:

  • metadata_enrichment_id - Identifier for the metadata enrichment.
  • container_id - The identifier of the project.
  • metadata_enrichment_name - The name of the metadata enrichment.

Postgres

CREATE TABLE statement:

create table metadata_enrichments(metadata_enrichment_id varchar(128) not null,
container_id varchar(36) not null,
metadata_enrichment_name varchar(256) not null,
tech_start TIMESTAMP(6) not null default CURRENT_TIMESTAMP,
tech_end TIMESTAMP(6) not null default to_timestamp('9999-12-30', 'YYYY-MM-DD'),
ts_id TIMESTAMP(6) not null default CURRENT_TIMESTAMP,
primary key(container_id,
metadata_enrichment_id))

ALTER TABLE statement:

alter table metadata_enrichments add constraint fk_metadata_enrichments_container_assets_1 foreign key (container_id,
metadata_enrichment_id) references container_assets(container_id,
asset_id) on
delete
    cascade on
    update
    no action

Db2

CREATE TABLE statement:

create table metadata_enrichments(metadata_enrichment_id varchar(128) not null,
container_id varchar(36) not null,
metadata_enrichment_name varchar(256) not null,
tech_start TIMESTAMP(12) not null IMPLICITLY HIDDEN generated always as row begin,
tech_end TIMESTAMP(12) not null IMPLICITLY HIDDEN generated always as row
end,
ts_id TIMESTAMP(12) not null generated always as transaction start ID,
primary key(container_id,
metadata_enrichment_id),
period SYSTEM_TIME (tech_start,
tech_end) ) ORGANIZE by row

ALTER TABLE statement:

alter table metadata_enrichments add constraint fk_metadata_enrichments_container_assets_1 foreign key (container_id,
metadata_enrichment_id) references container_assets(container_id,
asset_id) on
delete
    cascade on
    update
    no action

dq_problems table

This table contains information about all the quality problems that are defined for a project.

This table has the following columns:

  • problem_id - The identifier of the problem.
  • name - The name of the problem.
  • description - The description of the problem.

Postgres

CREATE TABLE statement:

create table dq_problems(problem_id varchar(128) not null,
name varchar(256) not null,
description clob,
tech_start TIMESTAMP(12) not null IMPLICITLY HIDDEN generated always as row begin,
tech_end TIMESTAMP(12) not null IMPLICITLY HIDDEN generated always as row
end,
ts_id TIMESTAMP(12) not null generated always as transaction start ID,
primary key(problem_id),
period SYSTEM_TIME (tech_start,
tech_end) ) ORGANIZE by row

Db2

CREATE TABLE statement:

create table dq_problems(problem_id varchar(128) not null,
name varchar(256) not null,
description text,
tech_start TIMESTAMP(6) not null default CURRENT_TIMESTAMP,
tech_end TIMESTAMP(6) not null default to_timestamp('9999-12-30', 'YYYY-MM-DD'),
ts_id TIMESTAMP(6) not null default CURRENT_TIMESTAMP,
primary key(problem_id))

dq_dimensions table

This table contains information about the quality dimensions for the rule.

This table has the following columns:

  • dimension_id - The identifier of the data quality dimension.
  • container_id - The identifier of the catalog or project.
  • name - The name of the data quality dimension.
  • description - The description of the data quality dimension.

Postgres

CREATE TABLE statement:

create table dq_dimensions(dimension_id varchar(128) not null,
container_id varchar(36) not null,
name varchar(256) not null,
description varchar(256) not null,
tech_start TIMESTAMP(6) not null default CURRENT_TIMESTAMP,
tech_end TIMESTAMP(6) not null default to_timestamp('9999-12-30', 'YYYY-MM-DD'),
ts_id TIMESTAMP(6) not null default CURRENT_TIMESTAMP,
primary key(dimension_id,
container_id))

ALTER TABLE statement:

alter table dq_dimensions add constraint fk_dq_dimensions_containers_1 foreign key (container_id) references containers(container_id) on
delete
    cascade on
    update
    no action

Db2

CREATE TABLE statement:

create table dq_dimensions(dimension_id varchar(128) not null,
container_id varchar(36) not null,
name varchar(256) not null,
description varchar(256) not null,
tech_start TIMESTAMP(12) not null IMPLICITLY HIDDEN generated always as row begin,
tech_end TIMESTAMP(12) not null IMPLICITLY HIDDEN generated always as row
end,
ts_id TIMESTAMP(12) not null generated always as transaction start ID,
primary key(dimension_id,
container_id),
period SYSTEM_TIME (tech_start,
tech_end) ) ORGANIZE by row

ALTER TABLE statement:

alter table dq_dimensions add constraint fk_dq_dimensions_containers_1 foreign key (container_id) references containers(container_id) on
delete
    cascade on
    update
    no action

dq_rule_definitions table

This table contains the actual metadata for data quality rule.

This table has the following columns:

  • rule_definition_id - The identifier of the data quality rule definition.
  • container_id - The identifier of the catalog or project.
  • expression - The expression of the data quality rule definition.
  • dq_dimension_id - The identifier of the data quality dimension.
  • name - The name of the data quality definition.

Postgres

CREATE TABLE statement:

create table dq_rule_definitions(rule_definition_id varchar(128) not null,
container_id varchar(36) not null,
expression text not null,
dq_dimension_id varchar(128),
name varchar(256) not null,
tech_start TIMESTAMP(6) not null default CURRENT_TIMESTAMP,
tech_end TIMESTAMP(6) not null default to_timestamp('9999-12-30', 'YYYY-MM-DD'),
ts_id TIMESTAMP(6) not null default CURRENT_TIMESTAMP,
primary key(rule_definition_id))

ALTER TABLE statements:

alter table dq_rule_definitions add constraint fk_dq_rule_definitions_containers_2 foreign key (container_id) references containers(container_id) on
delete
    cascade on
    update
    no action
alter table dq_rule_definitions add constraint fk_dq_rule_definitions_dq_dimensions_3 foreign key (dq_dimension_id,
container_id) references dq_dimensions(dimension_id,
container_id) on
delete
    cascade on
    update
    no action

Db2

CREATE TABLE statement:

create table dq_rule_definitions(rule_definition_id varchar(128) not null,
container_id varchar(36) not null,
expression clob not null,
dq_dimension_id varchar(128),
name varchar(256) not null,
tech_start TIMESTAMP(12) not null IMPLICITLY HIDDEN generated always as row begin,
tech_end TIMESTAMP(12) not null IMPLICITLY HIDDEN generated always as row
end,
ts_id TIMESTAMP(12) not null generated always as transaction start ID,
primary key(rule_definition_id),
period SYSTEM_TIME (tech_start,
tech_end) ) ORGANIZE by row

ALTER TABLE statements:

alter table dq_rule_definitions add constraint fk_dq_rule_definitions_containers_2 foreign key (container_id) references containers(container_id) on
delete
    cascade on
    update
    no action
alter table dq_rule_definitions add constraint fk_dq_rule_definitions_dq_dimensions_3 foreign key (dq_dimension_id,
container_id) references dq_dimensions(dimension_id,
container_id) on
delete
    cascade on
    update
    no action

dq_rules_defs table

This table contains details of binding between rule and definition as multiple bindings can be made.

This table has the following columns:

  • rule_id - The identifier of the data quality rule.
  • rule_definition_id - The identifier for the rule definition.
  • disambiguator - The disambiguator number.

Postgres

CREATE TABLE statement:

create table dq_rules_defs(rule_id varchar(128) not null,
rule_definition_id varchar(128) not null,
disambiguator integer,
tech_start TIMESTAMP(6) not null default CURRENT_TIMESTAMP,
tech_end TIMESTAMP(6) not null default to_timestamp('9999-12-30', 'YYYY-MM-DD'),
ts_id TIMESTAMP(6) not null default CURRENT_TIMESTAMP,
primary key(rule_id,
rule_definition_id))

ALTER TABLE statements:

alter table dq_rules_defs add constraint fk_dq_rules_defs_dq_rules_1 foreign key (rule_id) references dq_rules(rule_id) on
delete
    cascade on
    update
    no action
alter table dq_rules_defs add constraint fk_dq_rules_defs_dq_rule_definitions_2 foreign key (rule_definition_id) references dq_rule_definitions(rule_definition_id) on
delete
    cascade on
    update
    no action

Db2

CREATE TABLE statement:

create table dq_rules_defs(rule_id varchar(128) not null,
rule_definition_id varchar(128) not null,
disambiguator integer,
tech_start TIMESTAMP(12) not null IMPLICITLY HIDDEN generated always as row begin,
tech_end TIMESTAMP(12) not null IMPLICITLY HIDDEN generated always as row
end,
ts_id TIMESTAMP(12) not null generated always as transaction start ID,
primary key(rule_id,
rule_definition_id),
period SYSTEM_TIME (tech_start,
tech_end) ) ORGANIZE by row

ALTER TABLE statements:

alter table dq_rules_defs add constraint fk_dq_rules_defs_dq_rules_1 foreign key (rule_id) references dq_rules(rule_id) on
delete
    cascade on
    update
    no action
alter table dq_rules_defs add constraint fk_dq_rules_defs_dq_rule_definitions_2 foreign key (rule_definition_id) references dq_rule_definitions(rule_definition_id) on
delete
    cascade on
    update
    no action

dq_rules table

This table contains information about the data quality rules.

This table has the following columns:

  • rule_id - The identifier of the data quality rule.
  • container_id - The identifier of the catalog or project.
  • dq_dimension_id - The identifier of the data quality rule dimension.
  • name - The name of the data quality rule.
  • output_asset_id - The identifier of the output asset.
  • output_asset_container_id - The identifier of the output catalog or project.

Postgres

CREATE TABLE statement:

create table dq_rules(rule_id varchar(128) not null,
container_id varchar(36) not null,
dq_dimension_id varchar(128),
name varchar(256) not null,
output_asset_id varchar(128),
output_asset_container_id varchar(36),
tech_start TIMESTAMP(6) not null default CURRENT_TIMESTAMP,
tech_end TIMESTAMP(6) not null default to_timestamp('9999-12-30', 'YYYY-MM-DD'),
ts_id TIMESTAMP(6) not null default CURRENT_TIMESTAMP,
primary key(rule_id))

ALTER TABLE statement:

alter table dq_rules add constraint fk_dq_rules_dq_dimensions_5 foreign key (dq_dimension_id,
container_id) references dq_dimensions(dimension_id,
container_id) on
delete
    cascade on
    update
    no action

Db2

CREATE TABLE statement:

create table dq_rules(rule_id varchar(128) not null,
container_id varchar(36) not null,
dq_dimension_id varchar(128),
name varchar(256) not null,
output_asset_id varchar(128),
output_asset_container_id varchar(36),
tech_start TIMESTAMP(12) not null IMPLICITLY HIDDEN generated always as row begin,
tech_end TIMESTAMP(12) not null IMPLICITLY HIDDEN generated always as row
end,
ts_id TIMESTAMP(12) not null generated always as transaction start ID,
primary key(rule_id),
period SYSTEM_TIME (tech_start,
tech_end) ) ORGANIZE by row

ALTER TABLE statement:

alter table dq_rules add constraint fk_dq_rules_dq_dimensions_5 foreign key (dq_dimension_id,
container_id) references dq_dimensions(dimension_id,
container_id) on
delete
    cascade on
    update
    no action

dq_rule_bindings table

This table contains information about the Data Quality Rule Bindings.

This table has the following columns:

  • rule_id - The identifier of the data quality rule.
  • rule_definition_id - The identifier for the rule definition.
  • variable_name - The identifier of the variable that binds to column for data quality rule.
  • column_name - The name of the column.
  • container_id - The identifier of the catalog or project.
  • asset_id - The identifier of the asset.

Postgres

CREATE TABLE statement:

create table dq_rule_bindings(rule_id varchar(128) not null,
variable_name varchar(256) not null,
column_name varchar(256) not null,
container_id varchar(36) not null,
asset_id varchar(128) not null,
rule_definition_id varchar(128) default 'na' not null,
tech_start TIMESTAMP(6) not null default CURRENT_TIMESTAMP,
tech_end TIMESTAMP(6) not null default to_timestamp('9999-12-30', 'YYYY-MM-DD'),
ts_id TIMESTAMP(6) not null default CURRENT_TIMESTAMP,
primary key(rule_id,
rule_definition_id,
variable_name,
column_name))

ALTER TABLE statements:

alter table dq_rule_bindings add constraint fk_dq_rule_bindings_dq_rules_6 foreign key (rule_id) references dq_rules(rule_id) on
delete
    cascade on
    update
    no action
alter table dq_rule_bindings add constraint fk_dq_rule_bindings_container_data_asset_columns_7 foreign key (container_id,
asset_id,
column_name) references container_data_asset_columns(container_id,
asset_id,
name) on
delete
    cascade on
    update
    no action
alter table dq_rule_bindings add constraint fk_dq_rule_bindings_dq_rules_defs_3 foreign key (rule_id,
rule_definition_id) references dq_rules_defs(rule_id,
rule_definition_id) on
delete
    cascade on
    update
    no action

Db2

CREATE TABLE statement:

create table dq_rule_bindings(rule_id varchar(128) not null,
variable_name varchar(256) not null,
column_name varchar(256) not null,
container_id varchar(36) not null,
asset_id varchar(128) not null,
rule_definition_id varchar(128) default 'na' not null,
tech_start TIMESTAMP(12) not null IMPLICITLY HIDDEN generated always as row begin,
tech_end TIMESTAMP(12) not null IMPLICITLY HIDDEN generated always as row
end,
ts_id TIMESTAMP(12) not null generated always as transaction start ID,
primary key(rule_id,
rule_definition_id,
variable_name,
column_name),
period SYSTEM_TIME (tech_start,
tech_end) ) ORGANIZE by row

ALTER TABLE statements:

alter table dq_rule_bindings add constraint fk_dq_rule_bindings_dq_rules_6 foreign key (rule_id) references dq_rules(rule_id) on
delete
    cascade on
    update
    no action
alter table dq_rule_bindings add constraint fk_dq_rule_bindings_container_data_asset_columns_7 foreign key (container_id,
asset_id,
column_name) references container_data_asset_columns(container_id,
asset_id,
name) on
delete
    cascade on
    update
    no action
alter table dq_rule_bindings add constraint fk_dq_rule_bindings_dq_rules_defs_3 foreign key (rule_id,
rule_definition_id) references dq_rules_defs(rule_id,
rule_definition_id) on
delete
    cascade on
    update
    no action

dq_rule_execution table

This table contains information about the rule job for the data quality rule.

This table has the following columns:

  • dq_rule_id - The identifier of the data quality rule.
  • job_run_id - The identifier of the job for data quality rule job.
  • start_time - The start time of the job for data quality rule job.
  • end_time - The end time of the job for data quality rule job.
  • nb_tested_rows - The number of tested rows for the data quality rule job.
  • nb_passing_rows - The number of passing rows for the data quality rule job.
  • nb_failing_rows - The number of failing rows for the data quality rule job.
  • percent_passing_rows - The percentage of passing rows for the data quality rule job.
  • percent_failing_rows - The percentage of failing rows for the data quality rule job.
  • sampling_used - Specifies whether the sampling is used for the data quality rule.
  • sample_size - The sampling size for the data quality rule.
  • sample_type - The sampling type for the data quality rule.

Postgres

CREATE TABLE statement:

create table dq_rule_execution(dq_rule_id varchar(128) not null,
job_run_id varchar(256) not null,
start_time timestamp(6) not null,
end_time timestamp(6) not null,
nb_tested_rows bigint not null,
nb_passing_rows bigint not null,
nb_failing_rows bigint not null,
percent_passing_rows float not null,
percent_failing_rows float not null,
sampling_used boolean not null,
sample_size bigint,
sample_type varchar(256),
tech_start TIMESTAMP(6) not null default CURRENT_TIMESTAMP,
tech_end TIMESTAMP(6) not null default to_timestamp('9999-12-30', 'YYYY-MM-DD'),
ts_id TIMESTAMP(6) not null default CURRENT_TIMESTAMP,
primary key(dq_rule_id,
job_run_id))

ALTER TABLE statement:

alter table dq_rule_execution add constraint fk_dq_rule_execution_dq_rules_8 foreign key (dq_rule_id) references dq_rules(rule_id) on
delete
    cascade on
    update
    no action

Db2

CREATE TABLE statement:

create table dq_rule_execution(dq_rule_id varchar(128) not null,
job_run_id varchar(256) not null,
start_time timestamp(12) not null,
end_time timestamp(12) not null,
nb_tested_rows bigint not null,
nb_passing_rows bigint not null,
nb_failing_rows bigint not null,
percent_passing_rows float not null,
percent_failing_rows float not null,
sampling_used boolean not null,
sample_size bigint,
sample_type varchar(256),
tech_start TIMESTAMP(12) not null IMPLICITLY HIDDEN generated always as row begin,
tech_end TIMESTAMP(12) not null IMPLICITLY HIDDEN generated always as row
end,
ts_id TIMESTAMP(12) not null generated always as transaction start ID,
primary key(dq_rule_id,
job_run_id),
period SYSTEM_TIME (tech_start,
tech_end) ) ORGANIZE by row

ALTER TABLE statement:

alter table dq_rule_execution add constraint fk_dq_rule_execution_dq_rules_8 foreign key (dq_rule_id) references dq_rules(rule_id) on
delete
    cascade on
    update
    no action

category_custom_roles table

This table contains information about the custom category roles.

This table has the following columns:

  • role_id - The identifier of the category custom role.
  • role_name - The name of the category custom role.

Postgres

CREATE TABLE statement:

create table category_custom_roles(role_id varchar(32) not null,
role_name varchar(128) not null,
primary key(role_id))

Db2

CREATE TABLE statement:

create table category_custom_roles(role_id varchar(32) not null,
role_name varchar(128) not null,
primary key(role_id)) ORGANIZE by row

glossary_custom_relationship_def table

This table contains information about the custom relationship definitions.

This table has the following columns:

  • cr_definition_id - The identifier of the custom relationship definition.
  • artifact_id - The identifier of the custom relationship definition.
  • name - The name of the custom relationship definition.
  • created_on - The creation date of the custom relationship definition.
  • created_by - The person who created the custom relationship definition.
  • modified_on - The modification date of the custom relationship definition.
  • modified_by - The person who modified the custom relationship definition.
  • system_id - The system identifier where custom relationship definition is created.
  • type - The type of custom relationship definition.
  • reverse_name - The reverse relationship name of custom relationship definition.
  • description - The description of the custom relationship definition.
  • read_only - Specifies whether custom relationship definition is read only or not.
  • default_value - The default value of custom relationship definition.
  • multiple_values - Specifies whether custom relationship definition can have multiple values or not.

Postgres

CREATE TABLE statement:

create table glossary_custom_relationship_def(cr_definition_id varchar(128) not null,
artifact_id varchar(128) not null,
name varchar(256) not null,
created_on timestamp(6) not null,
created_by varchar(128) not null,
modified_on timestamp(6),
modified_by varchar(128),
system_id varchar(128),
type varchar(128) not null,
reverse_name varchar(256) not null,
description varchar(256),
read_only boolean not null,
default_value text,
multiple_values boolean not null,
tech_start TIMESTAMP(6) not null default CURRENT_TIMESTAMP,
tech_end TIMESTAMP(6) not null default to_timestamp('9999-12-30', 'YYYY-MM-DD'),
ts_id TIMESTAMP(6) not null default CURRENT_TIMESTAMP,
primary key(cr_definition_id))

Db2

CREATE TABLE statement:

create table glossary_custom_relationship_def(cr_definition_id varchar(128) not null,
artifact_id varchar(128) not null,
name varchar(256) not null,
created_on timestamp(12) not null,
created_by varchar(128) not null,
modified_on timestamp(12),
modified_by varchar(128),
system_id varchar(128),
type varchar(128) not null,
reverse_name varchar(256) not null,
description varchar(256),
read_only boolean not null,
default_value clob(128),
multiple_values boolean not null,
tech_start TIMESTAMP(12) not null IMPLICITLY HIDDEN generated always as row begin,
tech_end TIMESTAMP(12) not null IMPLICITLY HIDDEN generated always as row
end,
ts_id TIMESTAMP(12) not null generated always as transaction start ID,
primary key(cr_definition_id),
period SYSTEM_TIME (tech_start,
tech_end) ) ORGANIZE by row

glossary_ca_attr_artifact_type_assoc table

This table contains information about the supported artifact types for custom attribute definition.

This table has the following columns:

  • ca_definition_id - The identifier of the custom attribute definition.
  • artifact_type - The artifact type for which custom relationship definition is applicable.

Postgres

CREATE TABLE statement:

create table glossary_ca_attr_artifact_type_assoc(ca_definition_id varchar(128) not null,
artifact_type varchar(256) not null,
tech_start TIMESTAMP(6) not null default CURRENT_TIMESTAMP,
tech_end TIMESTAMP(6) not null default to_timestamp('9999-12-30', 'YYYY-MM-DD'),
ts_id TIMESTAMP(6) not null default CURRENT_TIMESTAMP,
primary key(ca_definition_id,
artifact_type))

ALTER TABLE statement:

alter table glossary_ca_attr_artifact_type_assoc add constraint fk_glossary_ca_attr_artifact_type_assoc_glossary_custom_attr_def_1 foreign key (ca_definition_id) references glossary_custom_attr_def(ca_definition_id) on
delete
    cascade on
    update
    no action

Db2

CREATE TABLE statement:

create table glossary_ca_attr_artifact_type_assoc(ca_definition_id varchar(128) not null,
artifact_type varchar(256) not null,
tech_start TIMESTAMP(12) not null IMPLICITLY HIDDEN generated always as row begin,
tech_end TIMESTAMP(12) not null IMPLICITLY HIDDEN generated always as row
end,
ts_id TIMESTAMP(12) not null generated always as transaction start ID,
primary key(ca_definition_id,
artifact_type),
period SYSTEM_TIME (tech_start,
tech_end) ) ORGANIZE by row

ALTER TABLE statement:

ALTER TABLE "BITNT2DBSAVIKASH1".glossary_ca_attr_artifact_type_assoc ADD CONSTRAINT fk_glossary_ca_attr_artifact_type_assoc_glossary_custom_attr_def_1 FOREIGN KEY (ca_definition_id) REFERENCES "BITNT2DBSAVIKASH1".glossary_custom_attr_def(ca_definition_id) ON DELETE CASCADE  ON UPDATE NO ACTION

glossary_custom_relationship_nodes table

This table contains information about the source and target artifact type for custom relationship definitions.

This table has the following columns:

  • cr_definition_id - The identifier of the custom relationship definition.
  • end1_artifact_type - The source artifact type of the custom relationships.
  • end2_artifact_type - The target artifact type of the custom relationships.

Postgres

CREATE TABLE statement:

create table glossary_custom_relationship_nodes(cr_definition_id varchar(128) not null,
end1_artifact_type varchar(128) not null,
end2_artifact_type varchar(128) not null,
tech_start TIMESTAMP(6) not null default CURRENT_TIMESTAMP,
tech_end TIMESTAMP(6) not null default to_timestamp('9999-12-30', 'YYYY-MM-DD'),
ts_id TIMESTAMP(6) not null default CURRENT_TIMESTAMP,
primary key(cr_definition_id,
end1_artifact_type,
end2_artifact_type))

ALTER TABLE statement

alter table glossary_custom_relationship_nodes add constraint fk_glossary_custom_relationship_nodes_glossary_custom_relationship_def_3 foreign key (cr_definition_id) references glossary_custom_relationship_def(cr_definition_id) on
delete
    cascade on
    update
    no action

Db2

CREATE TABLE statement:

create table glossary_custom_relationship_nodes(cr_definition_id varchar(128) not null,
end1_artifact_type varchar(128) not null,
end2_artifact_type varchar(128) not null,
tech_start TIMESTAMP(12) not null IMPLICITLY HIDDEN generated always as row begin,
tech_end TIMESTAMP(12) not null IMPLICITLY HIDDEN generated always as row
end,
ts_id TIMESTAMP(12) not null generated always as transaction start ID,
primary key(cr_definition_id,
end1_artifact_type,
end2_artifact_type),
period SYSTEM_TIME (tech_start,
tech_end) ) ORGANIZE by row

ALTER TABLE statement

alter table glossary_custom_relationship_nodes add constraint fk_glossary_custom_relationship_nodes_glossary_custom_relationship_def_3 foreign key (cr_definition_id) references glossary_custom_relationship_def(cr_definition_id) on
delete
    cascade on
    update
    no action

glossary_custom_attr_def table

This table contains information about the custom attribute definitions.

This table has the following columns:

  • ca_definition_id - The identifier of the custom attribute definition.
  • global_id - The global identifier of the custom attribute definition.
  • name - The name of the custom attribute definition.
  • created_on - The creation date of the custom attribute definition.
  • created_by - The person who created the custom attribute definition.
  • modified_on - The modification date of the custom attribute definition.
  • modified_by - The person who modified the custom attribute definition.
  • system_id - The system identified where custom attribute definition is created.
  • type - The type of custom attribute definition.
  • read_only - Specifies whether custom attribute definition is read only or not.
  • default_value - The default value of custom attribute definition.
  • multiple_values - Specifies whether custom attribute definition can have multiple values or not.

Postgres

CREATE TABLE statement:

create table glossary_custom_attr_def(ca_definition_id varchar(128) not null,
global_id varchar(256) not null,
name varchar(256) not null,
created_on timestamp(6) not null,
created_by varchar(128) not null,
modified_on timestamp(6),
modified_by varchar(128),
system_id varchar(128),
type varchar(128) not null,
read_only boolean not null,
default_value text,
multiple_values boolean not null,
tech_start TIMESTAMP(6) not null default CURRENT_TIMESTAMP,
tech_end TIMESTAMP(6) not null default to_timestamp('9999-12-30', 'YYYY-MM-DD'),
ts_id TIMESTAMP(6) not null default CURRENT_TIMESTAMP,
primary key(ca_definition_id))

Db2

CREATE TABLE statement:

create table glossary_custom_attr_def(ca_definition_id varchar(128) not null,
global_id varchar(256) not null,
name varchar(256) not null,
created_on timestamp(12) not null,
created_by varchar(128) not null,
modified_on timestamp(12),
modified_by varchar(128),
system_id varchar(128),
type varchar(128) not null,
read_only boolean not null,
default_value clob,
multiple_values boolean not null,
tech_start TIMESTAMP(12) not null IMPLICITLY HIDDEN generated always as row begin,
tech_end TIMESTAMP(12) not null IMPLICITLY HIDDEN generated always as row
end,
ts_id TIMESTAMP(12) not null generated always as transaction start ID,
primary key(ca_definition_id),
period SYSTEM_TIME (tech_start,
tech_end) ) ORGANIZE by row

glossary_ca_enum_list table

This table contains information about the custom attribute definitions of ENUM type.

This table has the following columns:

  • ca_definition_id - The identifier of the custom attribute definition of enum type.
  • value - The value of the custom attribute definition of enum type.
  • description - The description of the custom attribute definition.

Postgres

CREATE TABLE statement:

create table glossary_ca_enum_list(ca_definition_id varchar(128) not null,
value varchar(128) not null,
description varchar(256),
tech_start TIMESTAMP(6) not null default CURRENT_TIMESTAMP,
tech_end TIMESTAMP(6) not null default to_timestamp('9999-12-30', 'YYYY-MM-DD'),
ts_id TIMESTAMP(6) not null default CURRENT_TIMESTAMP,
primary key(ca_definition_id,
value))

ALTER TABLE statement:

alter table "BITNT2DBSAVIKASH1".glossary_ca_enum_list add constraint fk_glossary_ca_enum_list_glossary_custom_attr_def_2 foreign key (ca_definition_id) references "BITNT2DBSAVIKASH1".glossary_custom_attr_def(ca_definition_id) on
delete
    cascade on
    update
    no action

Db2

CREATE TABLE statement:

create table glossary_ca_enum_list(ca_definition_id varchar(128) not null,
value varchar(128) not null,
description varchar(256),
tech_start TIMESTAMP(12) not null IMPLICITLY HIDDEN generated always as row begin,
tech_end TIMESTAMP(12) not null IMPLICITLY HIDDEN generated always as row
end,
ts_id TIMESTAMP(12) not null generated always as transaction start ID,
primary key(ca_definition_id,
value),
period SYSTEM_TIME (tech_start,
tech_end) ) ORGANIZE by row

ALTER TABLE statement:

alter table glossary_ca_enum_list add constraint fk_glossary_ca_enum_list_glossary_custom_attr_def_2 foreign key (ca_definition_id) references glossary_custom_attr_def(ca_definition_id) on
delete
    cascade on
    update
    no action

governance_artifact_custom_attr_values table

This table contains information about the custom attribute values.

This table has the following columns:

  • artifact_id - The identifier of the custom relationship definition.
  • ca_definition_id - The identifier of the custom attribute definition.
  • value_id - The identifier of the custom attribute value.
  • text_value - The text value of custom attribute.
  • num_value - The numerical value of custom attribute.
  • date_value - The date value of custom attribute.

Postgres

CREATE TABLE statement:

create table governance_artifact_custom_attr_values(artifact_id varchar(128) not null,
ca_definition_id varchar(128) not null,
value_id varchar(128) not null,
text_value text,
num_value double precision,
date_value timestamp(6),
tech_start TIMESTAMP(6) not null default CURRENT_TIMESTAMP,
tech_end TIMESTAMP(6) not null default to_timestamp('9999-12-30', 'YYYY-MM-DD'),
ts_id TIMESTAMP(6) not null default CURRENT_TIMESTAMP,
primary key(artifact_id,
ca_definition_id,
value_id))

ALTER TABLE statement:

alter table governance_artifact_custom_attr_values add constraint fk_governance_artifact_custom_attr_values_glossary_custom_attr_def_12 foreign key (ca_definition_id) references glossary_custom_attr_def(ca_definition_id) on
delete
    cascade on
    update
    no action

Db2

CREATE TABLE statement:

create table governance_artifact_custom_attr_values(artifact_id varchar(128) not null,
ca_definition_id varchar(128) not null,
value_id varchar(128) not null,
text_value clob,
num_value double,
date_value timestamp(12),
tech_start TIMESTAMP(12) not null IMPLICITLY HIDDEN generated always as row begin,
tech_end TIMESTAMP(12) not null IMPLICITLY HIDDEN generated always as row
end,
ts_id TIMESTAMP(12) not null generated always as transaction start ID,
primary key(artifact_id,
ca_definition_id,
value_id),
period SYSTEM_TIME (tech_start,
tech_end) ) ORGANIZE by row

ALTER TABLE statement:

alter table governance_artifact_custom_attr_values add constraint fk_governance_artifact_custom_attr_values_glossary_custom_attr_def_12 foreign key (ca_definition_id) references glossary_custom_attr_def(ca_definition_id) on
delete
    cascade on
    update
    no action

artifact_category_associations table

This table contains information about the association between governance artifact and category.

This table has the following columns:

  • category_id- The identifier of the category of the artifact.
  • artifact_id - The identifier of the custom relationship definition.
  • relationship_type - The type of the relationship as identified from the artifact to category.
  • cr_definition_id - The identifier of the custom relationship definition.
  • reverse_relationship_type - The type of the relationship as identified from the category to artifact.

Postgres

CREATE TABLE statement:

create table artifact_category_associations(category_id varchar(128) not null,
artifact_id varchar(128) not null,
cr_definition_id varchar(128),
relationship_type varchar(256) not null,
reverse_relationship_type varchar(256),
tech_start TIMESTAMP(6) not null default CURRENT_TIMESTAMP,
tech_end TIMESTAMP(6) not null default to_timestamp('9999-12-30', 'YYYY-MM-DD'),
ts_id TIMESTAMP(6) not null default CURRENT_TIMESTAMP,
primary key(category_id,
artifact_id,
relationship_type))

ALTER TABLE statement:

alter table artifact_category_associations add constraint fk_artifact_category_associations_glossary_custom_relationship_def_9 foreign key (cr_definition_id) references glossary_custom_relationship_def(cr_definition_id) on
delete
    cascade on
    update
    no action

Db2

CREATE TABLE statement:

create table artifact_category_associations(category_id varchar(128) not null,
artifact_id varchar(128) not null,
cr_definition_id varchar(128),
relationship_type varchar(256) not null,
reverse_relationship_type varchar(256),
tech_start TIMESTAMP(12) not null IMPLICITLY HIDDEN generated always as row begin,
tech_end TIMESTAMP(12) not null IMPLICITLY HIDDEN generated always as row
end,
ts_id TIMESTAMP(12) not null generated always as transaction start ID,
primary key(category_id,
artifact_id,
relationship_type),
period SYSTEM_TIME (tech_start,
tech_end) ) ORGANIZE by row

ALTER TABLE statement:

alter table artifact_category_associations add constraint fk_artifact_category_associations_glossary_custom_relationship_def_9 foreign key (cr_definition_id) references glossary_custom_relationship_def(cr_definition_id) on
delete
    cascade on
    update
    no action

workflow_types

This table contains information about workflow types.

This table has the following columns:

  • type_id - Identifier for the workflow type.
  • name - Specifies name of the workflow type.
  • type - The type (for example governanance_artifacts).

Postgres

CREATE TABLE statement:

create table workflow_types(type_id varchar(128) not null,
name varchar(256) not null,
type varchar(256) not null,
tech_start TIMESTAMP(6) not null default CURRENT_TIMESTAMP,
tech_end TIMESTAMP(6) not null default to_timestamp('9999-12-30', 'YYYY-MM-DD'),
ts_id TIMESTAMP(6) not null default CURRENT_TIMESTAMP,
primary key(type_id))

Db2

CREATE TABLE statement:

create table workflow_types(type_id varchar(128) not null,
name varchar(256) not null,
type varchar(256) not null,
tech_start TIMESTAMP(12) not null IMPLICITLY HIDDEN generated always as row begin,
tech_end TIMESTAMP(12) not null IMPLICITLY HIDDEN generated always as row
end,
ts_id TIMESTAMP(12) not null generated always as transaction start ID,
primary key(type_id),
period SYSTEM_TIME (tech_start,
tech_end) ) ORGANIZE by row

workflow_templates table

This table contains information about the workflow templates.

This table has the following columns:

  • template_key - Identifier of the workflow template.
  • type_id - Identifier of the workflow type this template belongs to.
  • name - The name of the workflow template.
  • is_suspended - Specifies whether the workflow template is suspended or active(boolean).

Postgres

CREATE TABLE statement:

create table workflow_templates(template_key varchar(128) not null,
type_id varchar(128) not null,
name varchar(256) not null,
is_suspended boolean not null,
tech_start TIMESTAMP(6) not null default CURRENT_TIMESTAMP,
tech_end TIMESTAMP(6) not null default to_timestamp('9999-12-30', 'YYYY-MM-DD'),
ts_id TIMESTAMP(6) not null default CURRENT_TIMESTAMP,
primary key(template_key))

ALTER TABLE statement:

alter table workflow_templates add constraint fk_workflow_templates_workflow_types_1 foreign key (type_id) references workflow_types(type_id) on
delete
    cascade on
    update
    no action

Db2

CREATE TABLE statement:

create table workflow_templates(template_key varchar(128) not null,
type_id varchar(128) not null,
name varchar(256) not null,
is_suspended boolean not null,
tech_start TIMESTAMP(12) not null IMPLICITLY HIDDEN generated always as row begin,
tech_end TIMESTAMP(12) not null IMPLICITLY HIDDEN generated always as row
end,
ts_id TIMESTAMP(12) not null generated always as transaction start ID,
primary key(template_key),
period SYSTEM_TIME (tech_start,
tech_end) ) ORGANIZE by row

ALTER TABLE statement:

alter table workflow_templates add constraint fk_workflow_templates_workflow_types_1 foreign key (type_id) references workflow_types(type_id) on
delete
    cascade on
    update
    no action

workflow_configurations table

This table contains information about the workflow configurations.

This table has the following columns:

  • configuration_id - The identifier of the workflow configuration
  • name - The name of the workflow configuration
  • template_key - The identifier of the template to which the workflow belongs
  • state - Specifies whether the configuration is active or unavailable.

Postgres

CREATE TABLE statement:

create table workflow_configurations(configuration_id varchar(128) not null,
name varchar(256) not null,
template_key varchar(128) not null,
state varchar(256) not null,
tech_start TIMESTAMP(6) not null default CURRENT_TIMESTAMP,
tech_end TIMESTAMP(6) not null default to_timestamp('9999-12-30', 'YYYY-MM-DD'),
ts_id TIMESTAMP(6) not null default CURRENT_TIMESTAMP,
primary key(configuration_id))

ALTER TABLE statement:

alter table workflow_configurations add constraint fk_workflow_configurations_workflow_templates_2 foreign key (template_key) references workflow_templates(template_key) on
delete
    cascade on
    update
    no action

Db2

CREATE TABLE statement:

create table workflow_configurations(configuration_id varchar(128) not null,
name varchar(256) not null,
template_key varchar(128) not null,
state varchar(256) not null,
tech_start TIMESTAMP(12) not null IMPLICITLY HIDDEN generated always as row begin,
tech_end TIMESTAMP(12) not null IMPLICITLY HIDDEN generated always as row
end,
ts_id TIMESTAMP(12) not null generated always as transaction start ID,
primary key(configuration_id),
period SYSTEM_TIME (tech_start,
tech_end) ) ORGANIZE by row

ALTER TABLE statement:

alter table workflow_configurations add constraint fk_workflow_configurations_workflow_templates_2 foreign key (template_key) references workflow_templates(template_key) on
delete
    cascade on
    update
    no action

workflows table

This table contains information about the workflows.

This table has the following columns:

  • workflow_id - The identifier of the workflow.
  • configuration_id - The identifier of the configuration under which the workflow is created.
  • instance_state - The state of the instance, whether completed or failed.
  • workflow_state - The state of the workflow (for example "published").
  • created_by - The person who created the workflow.
  • start_time - The time at which the workflow started.
  • end_time- The time at which the workflow was completed.

Postgres

CREATE TABLE statement:

create table workflows(workflow_id varchar(128) not null,
configuration_id varchar(128),
instance_state varchar(256),
workflow_state varchar(256),
created_by varchar(128) not null,
start_time timestamp(6),
end_time timestamp(6),
tech_start TIMESTAMP(6) not null default CURRENT_TIMESTAMP,
tech_end TIMESTAMP(6) not null default to_timestamp('9999-12-30', 'YYYY-MM-DD'),
ts_id TIMESTAMP(6) not null default CURRENT_TIMESTAMP,
primary key(workflow_id))

ALTER TABLE statement:

alter table workflows add constraint fk_workflows_workflow_configurations_3 foreign key (configuration_id) references workflow_configurations(configuration_id) on
delete
    cascade on
    update
    no action

Db2

CREATE TABLE statement:

create table workflows(workflow_id varchar(128) not null,
configuration_id varchar(128),
instance_state varchar(256),
workflow_state varchar(256),
created_by varchar(128) not null,
start_time timestamp(12),
end_time timestamp(12),
tech_start TIMESTAMP(12) not null IMPLICITLY HIDDEN generated always as row begin,
tech_end TIMESTAMP(12) not null IMPLICITLY HIDDEN generated always as row
end,
ts_id TIMESTAMP(12) not null generated always as transaction start ID,
primary key(workflow_id),
period SYSTEM_TIME (tech_start,
tech_end) ) ORGANIZE by row

ALTER TABLE statement:

alter table workflows add constraint fk_workflows_workflow_configurations_3 foreign key (configuration_id) references workflow_configurations(configuration_id) on
delete
    cascade on
    update
    no action

workflow_tasks table

This table contains information about the workflow tasks.

This table has the following columns:

  • task_id - The identifier of the Workflow task
  • key - The current step of the workflow task (authoring, approval, review, publishing)
  • workflow_id - The identifier of the workflow under which the task belongs.
  • state - The state of the workflow task (for example "created").
  • assignee - The person who is assigned to this task.
  • create_time - The creation time of the workflow.
  • due_time - The due time of the workflow.
  • claim_time - The time at which the task was claimed.
  • end_time - The time at which the task ended.

Postgres

CREATE TABLE statement:

create table workflow_tasks(task_id varchar(128) not null,
key varchar(256),
workflow_id varchar(128),
state varchar(256),
assignee varchar(128),
create_time timestamp(6) not null,
due_time timestamp(6),
claim_time timestamp(6),
end_time timestamp(6),
tech_start TIMESTAMP(6) not null default CURRENT_TIMESTAMP,
tech_end TIMESTAMP(6) not null default to_timestamp('9999-12-30', 'YYYY-MM-DD'),
ts_id TIMESTAMP(6) not null default CURRENT_TIMESTAMP,
primary key(task_id))

ALTER TABLE statement:

alter table workflow_tasks add constraint fk_workflow_tasks_workflows_4 foreign key (workflow_id) references workflows(workflow_id) on
delete
    cascade on
    update
    no action

Db2

{#workflowtasks-db}

CREATE TABLE statement:

create table workflow_tasks(task_id varchar(128) not null,
key varchar(256),
workflow_id varchar(128),
state varchar(256),
assignee varchar(128),
create_time timestamp(12) not null,
due_time timestamp(12),
claim_time timestamp(12),
end_time timestamp(12),
tech_start TIMESTAMP(12) not null IMPLICITLY HIDDEN generated always as row begin,
tech_end TIMESTAMP(12) not null IMPLICITLY HIDDEN generated always as row
end,
ts_id TIMESTAMP(12) not null generated always as transaction start ID,
primary key(task_id),
period SYSTEM_TIME (tech_start,
tech_end) ) ORGANIZE by row

ALTER TABLE statement:

alter table workflow_tasks add constraint fk_workflow_tasks_workflows_4 foreign key (workflow_id) references workflows(workflow_id) on
delete
    cascade on
    update
    no action

Learn more

Parent topic: Setting up reporting for Watson Knowledge Catalog