ER/Studio

ER/Studio is data architecture and database design software developed by Embarcadero Technologies. ER/Studio is compatible with multiple database platforms and is used by data architects, data modelers, database administrators, and business analysts to create and manage database designs as well as document and reuse data assets.

IBM Automatic Data Lineage currently scans:

• Physical models

• Logical models

• Conceptual models

ER/Studio Scanner Overview

The ER/Studio scanner parses provided input DM1 specifications of ER/Studio models. The models can be of physical or logical layers. The physical layer can share a database connection configuration, and the logical layer provides a higher level of abstraction for the data visualization. The data lineage is interpolated from the physical to the logical layer by utilizing the mappings between physical and logical objects within the models. If the ER/Studio scanner and relevant database scanners are correctly configured, Automatic Data Lineage can enrich physical assets scanned from a database with metadata available in the ER/Studio model.

Supported Features

• Models for physical and logical layers

• Mapping between layers

• Asset metadata such as definitions and notes

• Table-level check constraint

• Column-level check constraint

• Column-level constraints: primary key and foreign key constraints

• Column-level metadata such as data type, data type length, and nullability

• Name and description of all constraints

Known Unsupported Features

Automatic Data Lineage does not support the following ER/Studio features. This list includes all of the features that IBM is aware are unsupported, but it might not be comprehensive.

• Visualization of ER relationships or referential integrity constraints

• Advanced foreign key constraints such as name or description

• Other types of table keys (e.g., alternate key)

• Other database constraints such as indexes or uniqueness

• Extraction of lineage from the model itself

• Analysis of SQL code within the model

Check out the guides below for more details on setting up this scanner.

• ER/Studio Integration Requirements
• ER/Studio Resource Configuration
• ER/Studio Manual Inputs

Extraction and Analysis Phase Scenarios

Extraction Phase

For the extraction phase for ER/Studio, there is only one scenario.

1. ER/Studio ingestion scenario - pulls inputs from git Manta Flow Agent Configuration for Extraction:Git Source or a remote agent filesystem location Manta Flow Agent Configuration for Extraction:Agent Source

Analysis Phase

For the analysis phase for ER/Studio models, there is only one scenario.

1. ER/Studio dataflow scenario — analyzes metadata from the provided ER/Studio models and and saves it in your Automatic Data Lineage metadata repository