Previous Topic: Example - Physical or Column Order in Forward EngineeringNext Topic: Forward and Reverse Engineering Indexes


Forward and Reverse Engineering Physical Storage Objects

When you generate the physical database schema from a physical model, you can include your defined physical storage objects as part of the schema. The physical object definitions are translated into the appropriate SQL CREATE statements and inserts the specified parameter information in the correct syntax.

When the schema is generated, the parent storage objects are created first, and then child storage objects and physical tables are created in the specified storage location. When you reverse engineer a database, you can import the names and definitions of physical storage objects defined on the target server in the same way it imports physical tables, indexes, and other physical schema information.

After you import physical storage objects into CA ERwin Data Modeler, you can view or modify the object definitions and table associations in the Physical Objects dialog and the Tables dialog using the standard editors.