0 / 0
Artifact relationships reporting tables

Artifact relationships reporting tables

Check the Postgres, Db2 statements for the tables that are related to artifact relationships.

Subject area Table name Description
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.
Artifact relationships artifact_category_associations The relationships between governance artifact and category.

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 
Db

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

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

Learn more

Parent topic: Reporting tables

Generative AI search and answer
These answers are generated by a large language model in watsonx.ai based on content from the product documentation. Learn more