Migrating ERwin models to ER/Studio. Plan, Convert, Validate

EMBARCADERO TECHNOLOGIESEMBARCADERO TECHNOLOGIES

Migration from ERwin® to

ER/Studio®

EMBARCADERO TECHNOLOGIES

Agenda

• Plan the Conversion– Perform an Inventory and Assessment of Current Models

– Define a Conversion Process

• Conversion Process– Converting from CA Erwin® 3.5.2 (ERX)

– Converting from Erwin® Data Modeler 4.1x and R7.x (MetaWizard)

• Validation of Conversion Process

2


Plan the Conversion

• Identify Inventory– Model Manager– Standalone

• Models in use– Nature of use (application specific, physically orientated)– Active Development– Deprecated

• Reverse Engineer Physical Models (1:1)

3

PERFORM AN INVENTORY AND ASSESSMENT OF CURRENTMODELS


Plan the Conversion

• Which models are to be converted to ER/Studio?• When should the models be converted?• Should ERwin physical models be validated and synched prior to

conversion? Or should this process be applied to the resulting ER/Studio models?

• Who will perform the conversion?• Who will be responsible for verifying the resulting conversion?• Who will be responsible for future maintenance of the ER/Studio

models?

4

DEFINE A CONVERSION PROCESS


Plan the Conversion

KEY FACTORS TO CONSIDER INCLUDE:

• Are the models stable and effectively complete? Or are they still under active modification?

• What type of databases, if any, are the models used to maintain? Are the database(s) maintained via tools other than the modeling tools?

5


Conversion Process

• Designed to help maintain investments in legacy models and metadata

• Conversion process depends on version of ERwin® in use.

6


Conversion Process

• ERX Import (legacy)

– Native ERX Import

– Directly imports the models

– Maximises the amount of information imported

– ERwin® v4.0 or later no longer support ERX Export

7


Conversion Process

1. Requires initial export from Erwin® using Files > Saves As… and selecting ERX file type

2. Launch ER/Studio.

3. Go to File > New.

4. Select the third option Import Model From: ERX File

8

CONVERTING FROM CA ERWIN 3.5.2


Conversion Process

• MetaWizard Import

– Uses ERwin® API

– Requires ERwin® to be installed on machine

– Requires a license for ER/Studio MetaWizard

– Imports the model metadata

– ERwin® v4.1 or ERwin® r7 and later

– File types supported, .er1, .erwin, .xml

9


Conversion Process

• Note: If you do not have ERwin® on the same machine as ER/Studio, you need to save the .er1 file as an .xml file prior to importing into ER/Studio.

• ERwin 4.1.x .er1 and r7 .erwin files are notorious for having corrupt data. Before saving the file as an .xml file, you should run their diagnostic check on the .er1 file.

– In ERwin go to Tools > Diagnostics10

CONVERTING FROM CA ERWIN DATA MODELER 4.1.XOR R7.X AND LATER


Conversion Process

1. Launch ER/Studio.

2. Go to File > New.

3. Select the last radio option, Import Model From:

4. Select External Metadata from the list. This launches MetaWizard.

11

• To import an ERwin .xml/.er1/.erwin file, perform the following:


Conversion Process

5. Select CA ERwin 7.x Data Modeler from the list.

6. Browse to the ERwin .xml file that you previously saved or the .er1/.erwin file if you intend to have the bridge do the conversion.

7. Click Next. MetaWizard validates the XML file for any errors or inconsistencies.

8. Click Finish. ER/Studio imports the Logical and Physical model.

12


Conversion Process

13


Conversion Process

14


Conversion Process

9. The file name defaults to the name of the ERwin file name with an extension of .dm1 (ER/Studio native file extension). Go to File > Save to save the model to your local drive or a network drive.

15


Conversion Process

16


Conversion Process

10. You may also opt to insert the models into ER/Studio Repository if it is installed. In this case log into the repository and go to Repository > Diagrams > Add Diagram... ER/Studio will launch a dialog to initialize some diagram information, such as author, diagram name, project, etc.

17


Validation of Conversion Process

In addition to converting the basic model objects such as entities, attributes, table, columns, etc, ER/Studio translates the ERwin file to ensure that other critical data is preserved, such as:

• ERwin Diagram Aesthetics (Layout, Color, Font, etc)• ERwin Subject Area Importation• ERwin UDP Importation• ERwin Domains, UDTs, Rules and Defaults• ERwin definitions and notes for model objects

18



Some physical information may be lost in translating the .xml files from version 4.1.x or r7.x, such as:

• ERwin triggers and procedure code

• ERwin macros

• Table storage parameters

• Storage objects

19



• Compare against live database– Recover missing physical information

– Validate the physical structure of tables, columns and foreign keys

• ER/Studio offers tools to validate logical metadata– Use Macros to Export to Microsoft® Excel reports

– Export attribute metadata, submodel usage of entities, domain usage, object definitions

– Compare against reports generated from Erwin®

20


Additional Resources

• http://docs.embarcadero.com/– Read Me file

– Quick Start Guide (Includes Installation and Tutorial Information)

– User Guide

– New Features Guide

• http://edn.embarcadero.com/– White Papers

– Articles

– Blogs

– Videos

– On-line Events

http://docs.embarcadero.com/

http://edn.embarcadero.com/


Technical Support

• Contact Details

– Form: http://support.embarcadero.com/forms/

– Phone: +44 (0) 1628 684499


Thank You

24

Data & Analytics

Migrating ERwin models to ER/Studio. Plan, Convert, Validate