Home
News
Meta Integration 06/2008 - Meta Integration releases
new Web 2.0 enabled MIMB 6.0
Site Map
Home <  width=46 height=34>

Meta Integration® Model Bridge (MIMB)
"Metadata Integration" Solution

MIMB Bridge Documentation

MIMB Import Bridge from Microsoft SQL Server Data Source View

Bridge Specifications

Vendor Microsoft
Tool Name SQL Server Data Source View (DSV)
Tool Version 7.0 to 9.0(2005)
Tool Web Site http://msdn.microsoft.com/en-us/library/ms174778.aspx
Supported Methodology [Data Modeling] Data Store (Physical Data Model), BI Design (RDBMS Source, Dimensional Target) via DSV XML File

Import tool: Microsoft SQL Server Data Source View (DSV) 7.0 to 9.0(2005) (http://msdn.microsoft.com/en-us/library/ms174778.aspx)
Import interface: [Data Modeling] Data Store (Physical Data Model), BI Design (RDBMS Source, Dimensional Target) via DSV XML File from Import bridge: 'MicrosoftSqlServerDsv' 6.0.3 - Nov 12 2008 19:27:47

Bridge Parameters

Parameter Name Description Type Values Default Mandatory
File This bridge imports an XML file with DSV or XMLA extension.

The file represents a data source view definition for Microsoft SQL Server 2005 Analysis Services.

Two options are available to retrieve such a file:

A) From SQL Server Business Intelligence Development Studio:
Each project contains one or more files with dsv extension.Such file can be selected and exported with the command: "File->Save .dsv As ..." to generate the DSV file. Or the file can be found in the project directory.

Each project contains one or more files with dsv extension.Such file can be selected and exported with the command: "File->Save .dsv As ..." to generate the DSV file. Or the file can be found in the project directory.

B) From SQL Server Management Studio:
SQL Server Management Studio can connect to an existingAnalysis Services server, which contains a list of data source views. Choose a data source view to be saved and use the command:"Script Database as->CREATE To -> File..." to generate a file with xmla extension.
FILE *.dsv
*.xmla
  Yes

 

Bridge Mapping

Meta Integration Repository (MIR)
Metamodel
(based on the OMG CWM standard)
"Microsoft SQL Server Data Source View"
Metamodel
Mapping Comments
     
AssociationRole Element Content  
Multiplicity   Based on Source information and KeyType attribute
Source   Based on Foreign Key information
AssociationRoleNameMap SourceField, TargetField  
Attribute Column  
Description msprop:Description Mapped only if comment is empty.
Name msprop:FriendlyName Attribute Name. Computed if not set
Optional minOccurs  
PhysicalName msprop:DbColumnName Attribute Physical Name.Computed from 'name' if not set
BaseType SourceField, TargetField BaseTypes are created to serve as parents for the simpleTypes defined in the file.
CandidateKey xs:unique  
PhysicalName name Class Physical Name.Computed from the 'name' if not set
UniqueKey   parent key attribute information
Class Table where msprop:TableType="Table"
CppClassType   Set to ENTITY
CppPersistent   Set to True
Description msprop:Description  
Name msprop:FriendlyName Class Name. Computed if not set
PhysicalName msprop:DbTableName Class Physical Name.Computed from the 'name' if not set
DatabaseCatalog Database Inferred from Table definition
DatabaseSchema Database schema Inferred from Table definition
DerivedType SimpleType In case of an Union, only the first item is used
Length length, totalDigits, maxLength, minLength  
LowerBound maxExclusive, maxInclusive  
Name name either explicitely in the file, or computed based on its usage
Scale fractionDigits  
UpperBound maxExclusive, maxInclusive  
UserDefined   True for simpleTypes defined in the file, False for those defined in the Schema specification
DesignPackage   No equivalent in XML. A main package "Logical View" is created to contain all elements.
Dimension DataTable, Named Query Represents the definition of logical table views, including calculated columns
Name Name  
DimensionAttribute Column, Calculated Column  
Name Name  
Position position  
ForeignKey SourceField, TargetField  
Index TargetIndex  
Name Name  
IndexMember TargetIndexField  
Position   position in XML file
Join Relationship  
Name name  
JoinRole Relationship 2 roles are created for each join Relationship
Model Schema The model is built using the elements contained in the file.
Name   Computed from the file name.
OlapSchema Data Source View An OLAPSchema is created to represent the collection of objects available in this DSV file available to Cube builders
SQLViewAttribute View Column  
SQLViewEntity View Tables withTableType=View

Last updated on Fri, 14 Nov 2008 20:26:25