Please note : This help page is not for the latest version of Enterprise Architect. The latest help can be found here.

Prev Next

DDL Transformation

The DDL transformation converts the logical model to a data model that is targeted at the default database type and that is ready for DDL generation. The data model can then be used to automatically generate DDL statements to run in one of the system-supported database products.

The DDL transformation uses and demonstrates support in the intermediary language for a number of database-specific concepts.




See also


Mapped one-to-one onto Class elements.

'Many-to-many' relationships are supported by the transformation, creating Join tables.


Mapped one-to-one onto attributes.

Primary Key

Lists all the columns involved so that they exist in the Class, and creates a Primary Key Method for them.

Foreign Key

A special sort of connector, in which the Source and Target sections list all of the columns involved so that:

  • The columns exist
  • A matching Primary Key exists in the destination Class, and
  • The transformation creates the appropriate Foreign Key
Transform Foreign Keys


  • You can define DBMS-specific aspects not depicted in a Logical model, such as Stored Procedures, Triggers, Views and Check Constraints, after the transformation; see the Physical Data Model topic


The PIM elements

After transformation, become the PSM elements

Generalizations are handled by providing the child element with a Foreign Key to the parent element, as shown. Copy-down inheritance is not supported.

Learn more