Reverse Engineer › Set Options for Reverse Engineer

Set Options for Reverse Engineer

After you select the model type, template, and database, you set options to reverse engineer specific objects.

To set options for reverse engineer

1. Click Reverse Engineer on the Tools menu.

   The Select Template dialog opens.

2. Select the new model type, template, and target database, then click Next.

   The Set Options dialog opens.

3. Complete the following fields:
   • Reverse Engineer From

     Select to reverse engineer from a database or script file. If you choose script file, click Browse to select the file.

   • Items to Reverse Engineer

     Displays the default option set, which includes all the objects and properties for the selected target server. You can create and save a new option set based on your requirements. Select or clear an object or property from the object tree to include or exclude it from the reverse engineer.

     Reverse Engineer System Objects

     Select to reverse engineer system and user tables, or only user tables. This field is only available when you reverse engineer from a database.

   • Table/Views In Owner:

     Select to reverse engineer tables and views by ownership. This field is only available when you reverse engineer from a database. This field has the following options:

     All

     Reverse engineer all tables and views in the database, regardless of the owner.

     Current

     Reverse engineer only those tables or views owned by the current user as entered in the <Database> Connection dialog.

     Owners (comma separated)

     Filter the tables or views that are reverse engineered to the tables or views owned by the owner name or names (separated by commas) specified in this box.

     In

     Opens the Filter By Table Container dialog to select one or more TABLESPACEs or databases that you want to reverse engineer.

   • Infer

     Indicate if you want to infer primary keys and relationships during reverse engineer. This field includes the following options:

     Primary Keys

     Infer primary key columns for tables based on defined indexes.

     Relations

     Infer relationships between tables based on either primary key column names or defined indexes, based on the Indexes and Names options.

     Indexes

     Infer relationships from the table indexes. When you click this button, the relationship between two tables is inferred only if the primary key columns of the parent table are in an index in the child table.

     Names

     Infer relationships from the primary key column names. When you click this button, a relationship is inferred between two tables if all of the primary key columns of the parent are in the child table.

     Note: If the target database or DDL script file supports primary key and foreign key declarations, you do not need to use the Primary Keys, Relations, Indexes, or Names options.

   • Case Conversion of Physical Names

     Select a choice for case conversion of physical names. You can convert names to lower or upper case, or select 'None' to preserve the case exactly as it appears in the script file or database.

   • Case Conversion of Logical Names

     Select a choice for case conversion of logical names. You can convert names to lower or upper case, or select 'None' to preserve the case exactly as it appears in the script file or database. Select 'Mixed' to preserve mixed-case logical names.

   • Include Generated Triggers

     Specify whether or not ERwin-generated triggers are loaded during the reverse engineer process. This option is linked to the "Automatically Create RI Triggers " setting in the Model Properties dialog, RI Default tabs. When you choose to Automatically create RI triggers, the triggers are treated as model objects and can be forward-engineered into a model, database, or script file. You can include or exclude these triggers when you reverse engineer.

4. Click Next.

   The database or script is processed and appears as a new model in the main workspace.

Note: When you reverse engineer from a database, you are prompted to connect to the database. If processing errors occur, a dialog displays that allows you to evaluate, display details for, and save the error message.