ERD To Data Model Transformation

The purpose of the Entity Relationship Diagram (ERD) to Data Model transformation is to create a data model from the ERD logical model, generating a model targeted at the default database type ready for DDL generation. Before doing the transformation, make sure you have defined the common data type for each attribute and selected a database type as the default database. The data modeling diagram can then be automatically generated. This data model can be used for generating DDL statements to run in one of the Enterprise Architect supported database products.

The transformation uses and demonstrates support in the intermediary language for the following database-specific concepts:


Mapped one-to-one onto Entity elements.


Mapped one-to-one onto attributes.

Primary Key

Comes from the primaryKey type of attribute.

Foreign Key

Make sure the primary key exists in the source Entity; the transformation then creates the appropriate foreign key.

The Source Entity Relationship Diagram:


After transformation becomes the Data Model Diagram (for an Oracle DBMS):



Sometimes you might go back to the ERD, make some changes and then want to do another transformation. To achieve better results, always delete the previous transformation package before doing the next transformation.


Generalization can be handled in ERD technology, as illustrated by the following example. Note that the copy-down inheritance is currently supported with two levels only.


This transforms to: