HOPEX Database Builder (Web) : MEGA Database Builder : Synchronizing logical and physical models
   
Synchronizing logical and physical models
 
"Logical to Physical" Synchronization Rules
Entities
Associations
From the Logical Model to the Physical Model
Running Synchronization (Logical > Physical)
Using Options (Logical > Physical)
Protecting Objects
Synchronization Results: Correspondences
Reduced Synchronization (Logical to physical mode)
Reduced Synchronization Source Objects (Logical > Physical)
Reduced Synchronization Strategies (Logical > Physical)
Running Reduced Synchronization (Logical > Physical)
Running Synchronization After Modifications
Synchronization after Modification of the Data Diagram
Synchronization after Modifications to the Physical Diagram
From the Physical Model to the Logical Model
"Physical to Logical" Synchronization Rules
Running Synchronization (Physical > Logical)
"Physical to Logical" Synchronization Results
Configuring Synchronization
Preparing Synchronization
Creation Options
Configuring Name Generation
Diagram Synchronization
Case of Diagram Update at Synchronization
Synchronization is a process that translates a data model expressed in entity/association formalism to a physical model expressed in relational formalism, and vice-versa. It therefore ensures correspondence of objects in the two models. The procedure should be carried out periodically. Throughout the modeling project, these models are each subject to their particular changes. Synchronization intervenes when we wish to compare the two models and automatically restore canonical mappings that connect them.
At synchronization, mapping rules are applied by default. You can modify mappings and arrange that synchronization keeps any customizations that have been carried out over time. See “Denormalizing logical and physical models", page 125.
Synchronization is carried out in the database editor. It is available with "Advanced" access to the HOPEX repository.
*Synchronization of models of a database can be in one direction or another - either in physical > logical direction or in logical > physical direction, but not both at the same time. When synchronization direction has been determined, synchronization should not be reversed. Mapping justification between the logical and physical levels is not guaranteed if this rule is not followed.