Microsoft SQL Server Repository 3.x (via MDC) - Unsupported EOL Bridge - Import
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 |
Data Profiling | |
Incremental Harvesting | |
Multi-Model Harvesting | |
Remote Repository Browsing for Model Selection |
SPECIFICATIONS
Tool: Microsoft / SQL Server Repository version 3.x via MDC XML File
See http://msdn.microsoft.com/library/default.asp?url=/library/en-us/reposad/raoverview_3t87.asp
Metadata: [Metadata Management] Metadata Repository, Data Store (Physical Data Model)
Component: MicrosoftSqlServerMdsMdc version 11.2.0
OVERVIEW
This bridge allows importing metadata from Microsoft Meta Data Services via a "Meta Data Coalition" (MDC) file.
Microsoft Meta Data Services is a part of SQLServer 2000 tools.
REQUIREMENTS
n/a
FREQUENTLY ASKED QUESTIONS
n/a
LIMITATIONS
Refer to the current general known limitations at https://metaintegration.com/Products/MIMB/Help/#!Documents/mimbknownlimitations.html
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
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' 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 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||
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. 'Auto Detect' Automatically detects the TypeSet used in the file. |
ENUMERATED |
|
Auto Detect | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||
DBM TypeSet | Used for DBM imports: Specifies the TypeSet, usually a database specific naming scheme, used to designate the column datatypes. 'Auto Detect' Automatically detects the TypeSet used in the file. |
ENUMERATED |
|
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 |