Microsoft SQL Server Repository 3.x (via MDC) - Unsupported EOL Bridge - 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 SQL Server Repository
Tool Version 3.x
Tool Web Site http://msdn.microsoft.com/library/default.asp?url=/library/en-us/reposad/raoverview_3t87.asp
Supported Methodology [Metadata Management] Metadata Repository, Data Store (Physical Data Model) via MDC XML File
Incremental Harvesting
Multi-Model Harvesting
Remote Repository Browsing for Model Selection
Data Profiling

Import tool: Microsoft SQL Server Repository 3.x (http://msdn.microsoft.com/library/default.asp?url=/library/en-us/reposad/raoverview_3t87.asp)
Import interface: [Metadata Management] Metadata Repository, Data Store (Physical Data Model) via MDC XML File from Microsoft SQL Server Repository 3.x (via MDC) - Unsupported EOL Bridge Import bridge: 'MicrosoftSqlServerMdsMdc' 10.1.0

Please enter a description


Bridge Parameters

Parameter Name Description Type Values Default Scope
File

When a model is currently loaded in Microsoft 'Repository Browser' tool:

1. Choose 'Export XML File' from the 'File' menu.

2. Browse to the directory in which you want to save the file and then type the file name for the model you are saving in the 'File Name' text box.

3. Click 'Save'.

The bridge will use the generated XML file as input.
FILE *.xml   Mandatory
Auto Correct The MDC file sometimes contain a slightly incomplete or incorrect model. This option allows you to specify whether the bridge should attempt to fix them or not.

'True' - Attempt to fix the model. This may involve deleting some elements but you will get warnings anyway.

'False' - Do not modify the model in any way, if the model is invalid it will be rejected by the validation phase if it is enabled.
BOOLEAN   True  
Model Filter Allows you to specify which model(s) to import in case the XML file contains more than one model.

'TestModel' will only import the model called 'TestModel', 'TestModel*' will import any model which name starts with 'TestModel', etc.
STRING      
Model Allows you to restrict the import to only models of a specific type.

'Any' - Import any type of model present in the file.

'UML' - Import only UML models.

'ERD' - Import only ERD models.

'DBM' - Import only DBM models.

'ERD and DBM' - Import only ERD and DBM models.
ENUMERATED
Any
UML
ERD
DBM
ERD and DBM
Any  
Top Package This option is used for two purposes. First, in MIR all model elements (classes, associations...) must belong to a package. So whenever an object is not explicitly associated to a package it is put in a special package and this specifies the name of that package. Second, if there is a single top level package in by that name in the model, we mark the package as optional so that it will not appear if the destination tool does not require all objects to be in a package. STRING   Logical View  
ERD TypeSet Used for ERD imports:

Specifies the TypeSet, i.e. the datatype naming convention, used to designate the datatypes of ERD Domains.

The default 'Auto Detect' automatically detects the TypeSet used in the file.
ENUMERATED
Auto Detect
Access 1.1
Access 2.0
Access 7
Access 97
AS/400 2
AS/400 3
AS/400 4.x
Clipper
DB2/390 5
DB2/CS 2
DB2/MVS 2
DB2/MVS 3
DB2/MVS 4
DB2/UDB 5
DBase 3
DBase 4
FoxPro
Informix 4.x
Informix 5.x
Informix 7.x
Informix 9.x
Ingres 6.4
Ingres 1.x
Ingres 2.x
InterBase
Oracle 7.0
Oracle 7.1
Oracle 7.2
Oracle 7.3
Oracle 8.x
Paradox 4.x
Paradox 5.x
Paradox 7.x
Progress 7.0
Progress 8.x
Rdb 4
Rdb 6
Rdb 7
Red Brick 3.0
Red Brick 4.0
Red Brick 5.x
SQL Anywhere 5
SQLBase 5.0
SQLBase 6.x
SQL Server 4.x
SQL Server 6.x
SQL Server 7.x
Sybase 4.2
Sybase 10
Sybase 11.x
Teradata 1
Teradata 2.x
Watcom 3
Watcom 4
XML Datatypes
Auto Detect  
DBM TypeSet Used for DBM imports:

Specifies the TypeSet, usually a database specific naming scheme, used to designate the column datatypes.

The default 'Auto Detect' automatically detects the TypeSet used in the file.
ENUMERATED
Auto Detect
Access 1.1
Access 2.0
Access 7
Access 97
AS/400 2
AS/400 3
AS/400 4.x
Clipper
DB2/390 5
DB2/CS 2
DB2/MVS 2
DB2/MVS 3
DB2/MVS 4
DB2/UDB 5
DBase 3
DBase 4
FoxPro
Informix 4.x
Informix 5.x
Informix 7.x
Informix 9.x
Ingres 6.4
Ingres 1.x
Ingres 2.x
InterBase
Oracle 7.0
Oracle 7.1
Oracle 7.2
Oracle 7.3
Oracle 8.x
Paradox 4.x
Paradox 5.x
Paradox 7.x
Progress 7.0
Progress 8.x
Rdb 4
Rdb 6
Rdb 7
Red Brick 3.0
Red Brick 4.0
Red Brick 5.x
SQL Anywhere 5
SQLBase 5.0
SQLBase 6.x
SQL Server 4.x
SQL Server 6.x
SQL Server 7.x
Sybase 4.2
Sybase 10
Sybase 11.x
Teradata 1
Teradata 2.x
Watcom 3
Watcom 4
XML Datatypes
Auto Detect  

 

Bridge Mapping

Meta Integration Repository (MIR)
Metamodel
(based on the OMG CWM standard)
"Microsoft SQL Server Repository 3.x (via MDC) - Unsupported EOL Bridge"
Metamodel
MicrosoftSqlServerMdsMdcDBM
Mapping Comments
     
Argument dbm:StoredProcedureParameter  
Comment comments  
DefaultValue defaultValue  
Description description  
Kind IsOutput  
Name name  
PhysicalName name  
Position   Order in the MDC DBM file
Association dbm:ReferentialConstraint  
Comment comments  
Description description  
ExtraConstraint DeleteRule, UpdateRule  
Name name  
PhysicalName name  
AssociationRole dbm:UniqueKeyRole / dbm:ForeignKeyRole  
Comment comments  
Description description  
Multiplicity   1' for the UniqueKeyRole if all the Attributes in the ForeignKey are mandatory and '0..1' otherwise. '0..*' for the ForeignKeyRole
Name name  
PhysicalName name  
Source   Set to 'true' for the UniqueKeyRole
AssociationRoleNameMap   Order in the MDC DBM file
Attribute dbm:Column  
Comment comments  
Description description  
InitialValue initialValue  
Name name  
Optional IsNullable  
PhysicalName name  
Position Ordinal  
CandidateKey dbm:UniqueKey  
Comment comments  
Description description  
Name name  
PhysicalName name  
UniqueKey   Set to 'true'
Class dbm:Table  
Comment comments  
CppClassType   Set to 'Entity'
CppPersistent   Set to 'true'
CppSpace EstimatedSize  
Description description  
Name name  
PhysicalName name  
DerivedType dbm:ColumnType  
Comment comments  
DataType name See the DataType Mapping section
Description description  
Length Length, NumericPrecision, TimePrecision From the Column's properties
Name name  
PhysicalName name  
Scale NumericScale From the Column's properties
UserDefined   Set to 'false'
DesignPackage dbm:Schema  
Comment comments  
Description description  
Name name  
PhysicalName name  
ForeignKey dbm:ForeignKey  
Comment comments  
Description description  
Name name  
PhysicalName name  
Index dbm:Index  
Comment comments  
Description description  
Name name  
PhysicalName name  
IndexMember dbm:IndexColumn  
Comment comments  
Description description  
Name name  
PhysicalName name  
Position   Order in the MDC DBM file
SortOrder IsAscending  
SQLViewAttribute   Not imported
SQLViewEntity dbm:LogicalView  
Comment comments  
Description description  
Name name If 'physicalName' is not set
PhysicalName name  
WhereClause Body  
StoreModel dbm:Catalog  
Comment comments  
Description description  
Name name  
PhysicalName name  
StoredProcedure dbm:StoredProcedure  
Comment comments  
CppAbstract   Not used in this class
CppConcurrency   Not used in this class
CppFriend   Not used in this class
CppScope   Not used in this class
CppStatic   Not used in this class
CppVirtual   Not used in this class
Description description  
Name name  
PhysicalName name  
Semantics body  
Synonym UML:TableSynonym  
Comment comments  
Description description  
Name name  
PhysicalName name