Microsoft Office Visio Database Diagram (via ERX) - Import

Bridge Specifications

Vendor	Microsoft
Tool Name	Office Visio Database Diagram
Tool Version	97 to 2016
Tool Web Site	http://microsoft.com/visio
Supported Methodology	[Data Modeling] Data Store (Physical Data Model, Logical Data Model) via erwin 3 (.ERX) File
Data Profiling
Incremental Harvesting
Multi-Model Harvesting
Remote Repository Browsing for Model Selection

SPECIFICATIONS
Tool: Microsoft / Office Visio Database Diagram version 97 to 2016 via erwin 3 (.ERX) File
See http://microsoft.com/visio
Metadata: [Data Modeling] Data Store (Physical Data Model, Logical Data Model)
Component: CaErwin3ErxImport.MicrosoftOfficeVisio version 11.2.0

OVERVIEW
This bridge imports data models from erwin Data Modeler, including logical only models with Entities, Attributes, Domains, physical only models with Tables, Columns, Data Types, or Logical/Physical models with both. This bridge also imports all relationships and their implementation (e.g. PK/FK) as well as the graphical layout of the data models (diagrams).
This bridge can import either the .ER1 format files or .ERX format files saved using erwin Data Modeler.
- erwin Native Format (.ER1):
This bridge requires the erwin Data Modeler COM/OLE API to be installed in order to parse .ER1 format files.
erwin Data Modeler must be properly installed with a valid license on the machine executing this bridge.
In order to test this, open an erwin model in Data Modeler and save it as 'XML Repository Format'.
- erwin Exchange Format (.ERX):
Here are the steps to create this type of .ERX file:
1. Choose 'Save As' from the 'File' menu.
2. Select the ERX format type.
3. Type the file name for the model you are saving in the 'File Name' text box (eventually press the browse button to select a specific directory).
4. Click 'OK'.

REQUIREMENTS
- erwin User:
This bridge must run on behalf of the Windows user that can run the erwin software.
If this bridge is running as part of a Windows desktop application, then you must log onto Windows with that user.
If this bridge is running as part of a Windows service, then go to the Windows services and click on the 'Properties' menu of such service, go to the 'Log On' tab, select 'This account' and specify the same user name and password used as Windows session when testing connectivity from erwin to the mart, and restart the Windows service.

FREQUENTLY ASKED QUESTIONS
Q: How does this bridge import the ordering of attributes?
A: This bridge imports the physical order preferably, if the information is present in the ERX file, otherwise the logical order is used.
To view the physical column ordering in erwin:
- Switch to the model Physical View,
- In the 'Format' menu, select 'Stored Display Settings...',
- Click on the 'Physical' tab, and select the 'Physical Order' radio button.
This is the order erwin uses when generating SQL DDL, and MIMB will import this order, if it is available in the file.
If you wish to import the logical order, please derive a logical only model in erwin and import it.

LIMITATIONS
Refer to the current general known limitations at https://metaintegration.com/Products/MIMB/Help/#!Documents/mimbknownlimitations.html

- Warning On Potential Missing Physical Names:
This issue is particularly relevant when converting from erwin to ETL or BI tools, or to the OMG CWM XMI standard.
When saving a logical and physical model, the physical names of tables, columns, and keys may not always be saved into the ERX file. When erwin is used to manage the automatic generation of physical names from logical names, only the generation rules are saved. This will obviously not be an issue for physical-only erwin models (which is often the case when re-engineering existing databases).
One solution is to make sure all physical names are explicitly set, therefore not relying on any generation rules from the logical names.
Alternatively, when saving a model as ERX, the dialog box offers a button called 'Expand...'. A new 'Expand Property Values' dialog box is then opened, select the database (e.g. Oracle, SQL Server) tab, and then check the appropriate names to expand (e.g. Col Name).

- Warning On Potential Missing Dimensional Modeling Roles:
This issue is particularly relevant when erwin is used for dimensional modeling to BI tools, or to the OMG CWM XMI standard. As for the physical name issue explained above, the dimensional modeling roles (Fact, Dimensional, or Outrigger) may not be available in the XML file if they are automatically calculated by erwin.
One solution, is to make sure all dimensional modeling roles are explicitly set (use the 'Table Editor', tab 'Dimensional'), therefore not relying on automatic calculations by erwin based on usage.

SUPPORT
Provide a troubleshooting package with debug log. Debug log can be set in the UI or in conf/conf.properties with MIR_LOG_LEVEL=6

Bridge Parameters

Bridge Mapping