Home
News
Meta Integration June 2011 - Meta Integration releases
new version 7
Site Map
Home <  width=46 height=34>

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

< Supported Tools | Readme < Description | About Standards  width=17 height=22>

MIMB Bridge Documentation

MIMB Import Bridge from Microsoft SQL Server Database (via JDBC)

Bridge Specifications

Vendor Microsoft
Tool Name SQL Server Database
Tool Version 7.0 to 10.5 (2008 r2)
Tool Web Site http://msdn.microsoft.com/en-us/library/bb418493.aspx
Supported Methodology [Database] Data Store (Physical Data Model, Expression Parsing) via JDBC API

Import tool: Microsoft SQL Server Database 7.0 to 10.5 (2008 r2) (http://msdn.microsoft.com/en-us/library/bb418493.aspx)
Import interface: [Database] Data Store (Physical Data Model, Expression Parsing) via JDBC API from Import bridge: 'JdbcMicrosoftSqlServer' 7.0.3 - 2012-02-02 21:54:47

IMPORTING FROM A MICROSOFT SQL SERVER DATABASE USING JDBC.

This bridge establishes a JDBC connection with a physical database in order to extract the physical metadata. It is critical that the parameters are filled correctly to satisfy the local connection requirements on the client workstation that is running the bridge. Please refer to the individual parameter's tool tips for more detailed examples.

Important note about permissions:
The username specified must have the VIEW DEFINITION and CONNECT permissions.

Bridge Parameters

Parameter Name Description Type Values Default Scope
Host Enter the host name or IP address where MS SQL Server database server is running (examples 1 and 2). Optionally, the parameter may contain a fully qualified JDBC connection string as defined for MS SQL Server (example 3).

Example #1:
someservername.com

Example #2:
192.169.10.20

Example #3:
jdbc:sqlserver://192.168.56.61:1433;databaseName=AdventureWorksDW;integratedSecurity=false;
STRING   localhost Mandatory
Port MS SQL Server database engine service port number. Default value is 1433.

For optimal connection performance, you should set the 'Port' option when you connect to a named instance.
This will avoid a round trip to the server to determine the port number.
If both a 'Port' option and 'Instance' option are used, the 'Port' option will take precedence and the 'Instance' option will be ignored.
NUMERIC      
Instance MS SQL Server instance name.

SQL Server 2000 and SQL Server 2005 allow for the installation of multiple database instances per server.
Each instance is identified by a specific name.
To connect to a named instance of SQL Server, you can either specify the port number of the named instance (preferred),
or you can specify the instance name.
STRING      
User The database user name on whose behalf the connection is being made.

The user should have at least the VIEW DEFINITION permission and a permission to CONNECT to the database.
STRING      
Password The database user's password on whose behalf the connection is being made PASSWORD      
Database This option can be used as a constraint to import a SQL Server database by specifying one database name.

The possible values are one database name: only the schemas and tables that belong to this database will be imported.

Example:
AdventureWorksDW - import tables from the 'AdventureWorksDW' database.
REPOSITORY_SUBSET     Mandatory
Schema This option can be used as a constraint to import a particular database Schema by specifying a list of schemas separated by semicolon.
You need set the 'Database' option to a valid database name before use the Schema 'Browse' command. It means, that for 'Browse' command and for 'Import' command the bridge gets database schemas list from selected above database only.
The possible values are:
- empty string: Only the Tables from a default Schema will be retrieved,
- a name or names: only the tables that belong to this schema(-s) will be imported.

Example:
schema1;schema2;schema3 - import metadata from the 'schema1', 'schema2' and 'schema3'.
REPOSITORY_SUBSET      
Import stored procedures Specifies if the Stored Procedures should be imported or not.

- 'False' : Stored Procedures are not imported(default)
- 'True' : Stored Procedures are imported
BOOLEAN   False  

 

Bridge Mapping

Meta Integration Repository (MIR)
Metamodel
(based on the OMG CWM standard)
"Microsoft SQL Server Database (via JDBC)"
Metamodel
Mapping Comments
     
Name Name  
Argument Procedure Column The stored procedure parameters are stored in the arguments
Description Comments on the column  
Kind Type The kind of parameter
Name Name  
Association Exported Keys  
Aggregation   True if all the attributes in the Exported Key a+C105re in the Primary Key
AssociationRole Exported Keys  
ExtraConstraint Update Rule, Delete Rule  
Multiplicity   Nullable property of the columns of the Exported Key
Source   Based on the multiplicity of each role
AssociationRoleNameMap Exported Keys The rolename map is created if the columns in the primary and foreign keys are different
Attribute Table Column  
Comment Comments on the column  
InitialValue Default value  
Name Name  
Optional Based on the nullable property  
PhysicalName Name  
Position Position If position is not provided, the order in which the attributes are retrieved is used.
BaseType Types  
DataType Data Type See datatype conversion array
Length Size  
Name   The name is computed from the datatype
PhysicalName Name  
Scale Maximum scale  
CandidateKey Index, Primary Key  
Name Name  
PhysicalName Name  
UniqueKey Non-Unique property  
Class Table of type "TABLE"
Comment Comments on the table  
CppClassType   Set to ENTITY
CppPersistent   Set to True
Name Name  
PhysicalName Name  
ClassDiagram Schema A class diagram is created for each package and contains all the elements of the package
DerivedType Column Table column, stored procedure column SQL View column or type
DataType Data Type See datatype conversion array
Length Size  
Name   The name is computed from the datatype
PhysicalName Name  
Scale Decimal digits  
UserDefined   True for Type
DesignPackage Schema A Package is created for each retrieved schema. If there is no schema a default package is created.
Name Name Set to "Schema" if there is no schema or the schema has no name.
ForeignKey Exported Keys  
Name Name  
PhysicalName Name  
Index Index, Primary Key, Exported Keys  
Clustered Index type true if index type is tableIndexClustered
Name Name  
PhysicalName Name  
IndexMember Index Member, Key Member  
Position Position in the Index or key  
SortOrder Ascending/descending order  
Model Catalog The model is built using the elements contained in the catalog (The database name used for catalog)
Name Name Set to MSSQLServer database name.
SQLViewAttribute View Column  
Comment Comments on the column  
Name Name  
PhysicalName Name  
Position Ordinal position  
SQLViewEntity Table of type "VIEW"
Comment Comments on the table  
Name Name  
PhysicalName Name  
StoredProcedure Stored Procedure  
Description Comments on the stored procedure  
Name Name  
Synonym Table Synonym  
Name Name  

Last updated on Thu, 2 Feb 2012 22:05:24