Microsoft Office Visio Database Diagram (via ERX) - Import - 7.1

Talend Data Catalog Bridges

author
Talend Documentation Team
EnrichVersion
7.1
EnrichProdName
Talend Big Data Platform
Talend Data Fabric
Talend Data Management Platform
Talend Data Services Platform
Talend MDM Platform
Talend Real-Time Big Data Platform
EnrichPlatform
Talend Data Catalog

Bridge Requirements

This bridge:
  • is only supported on Microsoft Windows.

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
Remote Repository Browsing for Model Selection
Data Profiling
Multi-Model Harvesting
Incremental Harvesting

Import tool: Microsoft Office Visio Database Diagram 97 to 2016 (http://microsoft.com/visio)
Import interface: [Data Modeling] Data Store (Physical Data Model, Logical Data Model) via erwin 3 (.ERX) File from Microsoft Office Visio Database Diagram (via ERX) Import bridge: 'CaErwin3ErxImport.MicrosoftOfficeVisio' 10.1.0


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 into 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 ERX 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.


Bridge Parameters

Parameter Name Description Type Values Default Scope
File When a model is currently loaded in erwin:

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'.

If you import the model from a different design tool, look at the documentation of this tool on how to generate the ERX file.

The bridge will use the generated ERX file as input.
FILE *.erx   Mandatory
Import UDPs A User Defined Property (UDP) is usually defined with a property definition object that has a default value. The objects the property applies to may also specify an explicit value for this property, or no value at all in which case the default value of the property definition applies.

This option allows you to control how property definitions and values are imported:

- By default, the bridge imports the property definition as a Property Type.

- 'As metadata' - Import an explicit value as Property Value, implicit values are not imported, the default value is kept on the Property Type only. This is the default behavior.

- 'As metadata, migrate default values' - Import explicit and implicit values as Property Value objects.

- 'In description, migrate default values' - Append the property name and value, even if implicit, to the object's description property only. This allows you to export the UDP values to another tool which does not support the notion of UDP.

- 'Both, migrate default values' - Import the UDP value, even if implicit, both as metadata and in the object's description.
ENUMERATED
As metadata
As metadata, migrate default values
In description, migrate default values
Both, migrate default values
As metadata  
Generate names for associations Generate a name for the associations and generalizations. These objects are unnamed in erwin. False is the default. BOOLEAN   False  
Encoding Specifies the character set encoding of the model to be imported or exported. If there are multiple choices for a language, the actual encoding will be indicated between parentheses. The default is 'Western European (Windows 1252)' on Windows and 'Western European (ISO 8859-1)' on other platforms. ENUMERATED
Central and Eastern European (iso-8859-2)
Central and Eastern European (windows-1250)
Chinese Traditional (big5)
Chinese Simplified (GB18030)
Chinese Simplified (GB2312)
Cyrillic (iso-8859-5)
Cyrillic (windows-1251)
DOS (ibm-850)
Greek (iso-8859-7)
Greek (windows-1253)
Hebrew (iso-8859-8)
Hebrew (windows-1255)
Japanese (shift_jis)
Korean (ks_c_5601-1987)
Thai (TIS620)
Thai (windows-874)
Turkish (iso-8859-9)
Turkish (windows-1254)
UTF 8 (utf-8)
UTF 16 (utf-16)
Western European (iso-8859-1)
Western European (iso-8859-15)
Western European (windows-1252)
Locale encoding
No encoding conversion
windows-1252  
Import subject areas Specifies how to import the subject areas from erwin:

'As diagrams' - import as diagrams only.
'As packages and diagrams' - import as packages and diagrams. This is the default.
'Do not import subject areas' - do not import subject areas.

This option may be useful to some database modelers who decided to save the hierarchy structure of subject areas.
ENUMERATED
As diagrams
As packages and diagrams
Do not import subject areas
As packages and diagrams  

 

Bridge Mapping

Meta Integration Repository (MIR)
Metamodel
(based on the OMG CWM standard)
"Microsoft Office Visio Database Diagram (via ERX)"
Metamodel
CaErwin3Erx
Mapping Comments
     
Association Relationship  
Aggregation Identifying/ Non Identifying True if identifying
Description Definition optional: UDP values can be added to the description
DesignLevel Logical Only/Physical Only  
PhysicalName Foreign Key Constraint Name  
DesignLevel Logical Only/Physical Only  
ExtraConstraint Delete, Insert, Update Rule  
Multiplicity Cardinality  
Name Verb Phrase  
Source   Based on the multiplicity of each role
AssociationRoleNameMap Attribute/Index The association between the primary key column and the foreign key column
Attribute Attribute/Column  
Description Definition optional: UDP values can be added to the description
DesignLevel Logical Only/Physical Only  
Name Logical Name  
Optional Null Option  
PhysicalName Physical Name  
Position Column Position  
BaseType Domain, Attribute Data Type  
DataType Data Type See datatype conversion array
Description Definition  
Length Data Type Length  
Name Name  
PhysicalName Validation Rule Name/DataType Derived from the datatype
Scale Data Type Precision  
CandidateKey Key Group/Index (non Foreign Key)  
Name Logical Name if set by the user
PhysicalName Physical Name if set by the user
UniqueKey   True for Primary Key/Alternate Key
Class Entity/Table  
Comment Table Comment  
CppClassType   Set to ENTITY
CppPersistent   Set to True
Description Definition optional: UDP values can be added to the description
DesignLevel Logical Only/Physical Only  
DimensionalRole Dimensional Modeling Role  
Name Logical Name  
PhysicalName Physical Name  
ClassDiagram Subject Area  
Description Definition optional: UDP values can be added to the description
Name Name  
DatabaseSchema Owner Table, View or Index owner
Name Name  
DerivedType Domain, Attribute Data Type, Validation Rule  
DataType Data Type See datatype conversion array
Description Definition  
Length Data Type Length  
LowerBound Validation Rule Minimum  
Name Name  
PhysicalName Validation Rule Name/DataType Derived from the datatype
Scale Data Type Precision  
UpperBound Validation Rule Maximum  
UserDefined   True for User Defined Domain
DesignPackage   No equivalent in ERwin. A main package "Logical View" will be created to contain all entities/references
ForeignKey Key Group/Index (Foreign Key)  
Name Logical Name if set by the user
PhysicalName Physical Name if set by the user
Generalization Supertype/Subtype  
GeneralizationRole Supertype/Subtype Relationship  
Index Key Group/Index  
Name Logical Name if set by the user
PhysicalName Physical Name if set by the user
IndexMember Key Group Member/Index Member Associated with each attribute in a key
Position Column Position  
SortOrder Ascending/descending order  
Note Note  
Projection Diagram View Object Graphical Information
BackgroundColor fill color  
FontColor font color  
FontName font  
FontSize font size  
Height height  
LineColor line color  
Width width  
X x  
Y y  
RelationshipProjection Diagram View Object Graphical Information
FontName font  
FontSize font size  
LineColor line color  
LinePoints relationship path  
X x relationship mid point
Y y relationship mid point
SQLViewAssociation View Relationship  
SQLViewAttribute View Column  
Description Comment  
Name Name  
PhysicalName Name  
Position Column Position  
SQLViewEntity View Table  
Description Comment  
Name Name  
PhysicalName Name  
WhereClause SQL statement  
Shape Text Block  
Bold Text Font Style User settable
FontColor Text Block Color  
FontName Text Block Font Font typeface name
FontSize Text Size  
Height   Calculated property
Italic Text Font Style User settable
Name   Computed parameter, based on the object ID
ShapeType   Rectangle
Strike Text Effects Strikeout User settable
Underline Text Effects Underline User settable
Width   Calculated property
X   Calculated property
Y   Calculated property
Z   Calculated property
StoreModel Model/Diagram The model is built using the elements contained in the ERwin file
Description Definition  
Name Name Diagram name or derived from the ERwin file name
SystemType Target Server  
SystemTypeOld Target Server  
Name Display Value/Valid Value  
TypeValue Validation Rule  
Name Display Value/Valid Value  
Position Order Sequence  
Value Value