After you select the model type, template, and database, set the options to reverse engineer specific objects. The options that you select here determine the objects that are included in the model. However, when you reverse engineer from a script, these options are overridden and all the objects are reverse engineered.
The modeling tool builds its models by querying the system catalog of the database, rather than querying the specific objects. You must have read and write permissions on all the objects that you want to reverse engineer.
Follow these steps:
The Reverse Engineer - Select Template dialog opens.
The Reverse Engineer - Set Options dialog opens.
Specifies whether you want to reverse engineer from a database or a script. If you choose the script, click Browse to select the file.
Note: To reverse engineer from a script, select a file that is saved either in ANSI or ASCII format.
Lets you select the naming standard glossary file (.CSV) that you want to apply to your model.
Displays the default option set, which includes all the objects and properties for the selected target database. You can change the default option set and save it for future use. The option set can be saved as a model or as an XML file. If you save the option set as a model, the options are applicable only to that model. If you save the option set as an XML file, you can use it with other models as well.
Reverse Engineer
Specifies whether you want to reverse engineer system objects and user tables, or only user tables. If you select the System Objects check box the system tables, views and stored procedures related to system tables are reverse engineered.
Reverse engineers tables and views by ownership. You must have read and write privileges on all the tables that you want to reverse engineer, regardless of whether you are the owner of the table. Select one of the following ownership options:
Reverse engineers all tables and views in the database for which you have the necessary permissions, regardless of the owner.
Reverse engineers only those tables and views that are owned by the current user. The current user details are entered in the <Database> Connection dialog.
Reverse engineers the tables and views that are owned by the users that are specified here. Enter the user names in capital letters.
Specifies whether you want to infer primary keys or relationships, or both, during reverse engineering. Work with the following options:
Infers primary key columns for the tables that are based on defined indexes.
Infers the relationships between tables that are based on either primary key column names or defined indexes. Select this option and then specify whether to use primary key column names or defined indexes:
Indexes
Infers the relationships from the table indexes. Relationships are inferred from table indexes only if the primary key columns of the parent table are part of the index in the child table.
Names
Infers the relationships from the primary key column names. Relationships are inferred from columns names only if all of the primary key columns of the parent are in the child table.
Note: If the target database or script supports primary and foreign key declarations, you do not need to use the Primary Keys, Relations, Indexes, or Names options.
Specifies how the case conversion of physical names is handled during reverse engineering. Work with the following options:
Preserves the case exactly as it appears in the script file or database.
Converts the names to lower case.
Converts the names to upper case.
Overrides the physical name property for all objects in logical/physical models automatically during reverse engineering.
If this option is not enabled, all logical and physical names are set to the same value after the process completes. If this option is enabled, the logical/physical link is broken between the logical and physical name.
Specifies how the case conversion of logical names is handled during reverse engineering. Work with the following options:
Preserves the case exactly as it appears in the script file or database.
Converts the names to lower case.
Converts the names to upper case.
Preserves mixed-case logical names.
Specifies whether erwin-generated triggers are loaded during the reverse engineer process. This option is linked to the Automatically Create RI Triggers setting in the Model Editor, RI Defaults tab. When you choose to create RI triggers automatically, the triggers are treated as model objects. These objects can be forward-engineered into a model, database, or script file. You can include or exclude automatically generated triggers when you reverse engineer.
If you are using a script, the script is processed and displayed as a new model in the main workspace.
|
Copyright © 2017 erwin Inc.
All rights reserved.
|
|