 |
|
|||||||
 |
   
|
|
||||||
|
|
|||||||
|
|
|
||||||
| Vendor | Microsoft |
| Tool Name | SQL Server Database |
| Tool Version | 7.0 to 10.0 (2008) |
| 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.0 (2008) (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' 6.1.0 - Mar 2 2010 19:13:17
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 for the local connection requirements on the client workstation that is running the bridge. Please refer to the individual parameter tools tips for more detailed examples by database type.
Important note about permissions:
The user should have the VIEW DEFINITION and CONNECT permissions.
| Parameter Name | Description | Type | Values | Default | Scope |
| Host | Host name or IP address where MS SQL Server database server is running. |
STRING | localhost | Mandatory | |
| Port | MS SQL Serevr database engine service port number. Default value is 1433. |
NUMERIC | 1433 | Mandatory | |
| Instance | MS SQL Server 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 | |||
| Catalog/Schema | This option can be used as a constraint to import a particular database Catalog and Schema by specifying a list of catalog and/or catalog.schema pairs separated by semicolon. The possible values are: - empty string: Only the Tables from a default Catalog\Schema will be retrieved, - a name or names: only the tables that belong to this catalog(-s) [catalog(-s) snd schema(-s)] will be imported. Example: catalog1.schema1;catalog2 - import metadata from the 'catalog1' schema with name 'schema1' and all accessible schemas from 'catalog2'. catalog1.schema1;catalog2.schema1;catalog2.schema2 - import metadata from 'schema1' within the catalogs 'catalog1' and 'catalog2' and the schema with name 'schema2' from 'catalog2'. |
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 |
| 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 |
Last updated on Tue, 2 Mar 2010 19:24:00
