Synchronization
Open ModelSphere's synchronization function allows you to compare
models' information representing the DBMS schema and the DBMS
schema itself (physical model). The results of the comparison are presented
in a comprehensive interface; the function synchronizes the two
models to generate a comparison report.
Process
The synchronization is based on data model information (the feature is available on
a data model selection).
The synchronization process compares objects from:
Data model: The data model linked to the database.
Database: The database associated with the model.
Operation library: The operation library linked to the database.
Domain and user type: Domain and user type referred to in the data model
and the operation library.
To use the synchronization feature:
- In the explorer window, select the database (it will become highlighted)
- Select Tools > Database > Synchronization.
NOTE: Before synchronizing two
models, do not forget to
validate your models.
Model selection
The function will prompt you to select the database model. It can be an existing data
model or a model created from a DBMS connection during the synchronization process.
Options
You can select the concepts and descriptors that will be used for the comparison of
the two models.
Concepts to synchronize (Scope): Provide integration parameters (the same parameters can be used
for the integration and the synchronization) to control the concepts
and descriptors on which synchronization's actions will be applied.
Load and save existing synchronization scope to a file. The synchronization
parameters are specific to the target system.
SQL script output (Generate object with user): It is possible to define users in ModelSphere. They can be used as
database objects' owners. If you have done so, and the synchronization
needs to generate DDL for a database object, the physical name
will be prefixed by the corresponding user's physical name (ex: create
table jeff.employee)
Database options (Synchronize using user): The reverse will extract object's owner information from the database
and will use it in the matching process.
DBMS options: This part is for the specific DBMS reverse engineering options. Available only with a connection. (See Reverse Engineering).
Synchronization interface
The upper portion of the interface displays SMS and physical model information,
side by side, in a tree structure similar to the application explorer. It uses a color
code to ease the identification of model similarities and differences.
BLUE The object only exists in ModelSphere's model
GREEN The object only exists in the physical model
RED Objects are different
BLACK Objects are identical
The lower portion displays object property differences if there are any.
Object and property actions
After comparing and displaying model differences, the user can modify these models
in a selective manner, and in any direction. However, it is important to specify
that all object actions are applied hierarchically on the object selection. For example,
if the action is changed on the table 'employee' it will affect all of the refering column’s
actions. Therefore, it is important to start assigning actions from the highest to the
lowest level of composition. Here are the actions available:
- Merge: Source model objects are added to the target model to form a super-set of
all model components. (Add/modify)
- Replace : The target model information is replaced by the source model information.
Any additional information in the target is deleted.
- None : No action will be applied on the object and its descendants.
- Associate : Link two objects so they are considered equivalents and will be compared.
- Break Association : Unlink two objects so they are not considered equivalents and will not be
compared.
It is possible to decide upon the objects which do not have equivalence in the other models :
- Add : Add the object in the model where it's missing.
- Delete : Delete the object in the model where it is.
There are also actions available on object property differences:
- Modify in ModelSphere : Modify the application model.
- Modify in Physical : Modify the physical by generating a DDL script with the SQL clauses.
- Display Values : Offers a larger size display of source and target values.
Report
A report is always produced at the end of the synchronization process. It identifies
the two models, the date, the list of differences and the modifications applied to the
model or physical model.
For impact analysis purposes, this report can also be produced before
the synchronization is completed.