Bridge Specifications
| Vendor | Microsoft |
| Tool Name | SQL Server Integration Services (SSIS) |
| Tool Version | 11.0 (2012) to 15.x (2019) |
| Tool Web Site | https://docs.microsoft.com/en-us/sql/integration-services/ |
| Supported Methodology | [Data Integration] Multi-Model, Metadata Repository, ETL (Source and Target Data Stores, Transformation Lineage, Expression Parsing) via JDBC API |
SPECIFICATIONS
Tool: Microsoft / SQL Server Integration Services (SSIS) version 11.0 (2012) to 15.x (2019) via JDBC API
See https://docs.microsoft.com/en-us/sql/integration-services/
Metadata: [Data Integration] Multi-Model, Metadata Repository, ETL (Source and Target Data Stores, Transformation Lineage, Expression Parsing)
Component: MicrosoftSqlServerRepositoryIsDb version 11.2.0
DISCLAIMER
This import bridge requires internet access to download third-party libraries:
- such as https://repo.maven.apache.org/maven2/ to download open source third-party libraries,
- and more sites for other third-party software such as database specific JDBC drivers.
The downloaded third-party libraries are stored into $HOME/data/download/MIMB/
- If HTTPS fails, the import bridge then tries with HTTP.
- If a proxy is used to access internet, you must configure that proxy in the JRE (see the -j option in the Miscellaneous parameter).
- If the import bridge does not have full access to internet, that $HOME/data/download/MIMB/ directory can be copied from another server with internet access where the command $HOME/bin/MIMB.sh (or .bat) -d can be used to download all third-party libraries used by all bridges at once.
By running this import bridge, you hereby acknowledge responsibility for the license terms and any potential security vulnerabilities from these downloaded third-party software libraries.
OVERVIEW
The bridge imports Packages from a corresponding SQL Server SSIS Catalog using a JDBC connection.
REQUIREMENTS
Note that SQL Server no longer supports TLS v1 and v1.1 and instead require TLS 1.2 for security reasons: In addition the JDK 11.0 disables any out of dates TLS versions such as 1.0 and 1.1 by default.
https://support.microsoft.com/en-us/topic/kb3135244-tls-1-2-support-for-microsoft-sql-server-e4472ef8-90a9-13c1-e4d8-44aad198cdbe#:%7E:text=SQL%20Server%202019%20has%20the,to%20enable%20TLS%201.2%20support
Therefore, if SQL Server cannot be upgraded to TLS 1.2, then the JDK 11 configuration must be modified by editing the file: /MetaIntegration/jre/conf/security/java.security
and remove "TLSv1, TLSv1.1," in the following line:
- jdk.tls.disabledAlgorithms=SSLv3, TLSv1, TLSv1.1, RC4, DES, MD5withRSA, \
which should then look like:
- jdk.tls.disabledAlgorithms=SSLv3, RC4, DES, MD5withRSA, \
FREQUENTLY ASKED QUESTIONS
n/a
LIMITATIONS
Refer to the current general known limitations at http://metaintegration.com/Products/MIMB/MIMBKnownLimitations.html or bundled in Documentation/ReadMe/MIMBKnownLimitations.html
SUPPORT
Provide a troubleshooting package with:
- the debug log (can be set in the UI or in conf/conf.properties with MIR_LOG_LEVEL=6)
- the metadata backup if available (can be set in the Miscellaneous parameter with -backup option, although this common option is not implemented on all bridges for technical reasons).
Bridge Parameters
| Parameter Name | Description | Type | Values | Default | Scope | |||||||||||||||||||||||||
| Host | Host name or IP address where SQL Server Catalog is stored. | STRING | localhost | Mandatory | ||||||||||||||||||||||||||
| User | The database username on whose behalf the connection is being made. The SISS DB bridge connects directly to the SQL Server repository database. Thus, this user is a database user, not part of the integrated SSIS permissions. You should grant the following database permissions to this user: - Server Roles: public for Connect access - Database Membership: db_reader, ssis_admin. Note, the ssis_admin membership is required for accessing internal stored procedures to extract packages. |
STRING | ||||||||||||||||||||||||||||
| Password | The database user's password on whose behalf the connection is being made. | PASSWORD | ||||||||||||||||||||||||||||
| Database | The name of the database. | STRING | SSISDB | Mandatory | ||||||||||||||||||||||||||
| Browse Folder Filter | Enter the folder name of Package(s) within the SQL Server Integration Service catalog. This parameter should be utilized if there is a requirement to limit the scope of repository structure browsing. If specified, the bridge will only import packages from the specified folders. | REPOSITORY_SUBSET | ||||||||||||||||||||||||||||
| Packages | SQL Server Integration Service package names to be processing. | REPOSITORY_SUBSET | Mandatory | |||||||||||||||||||||||||||
| Variable values file | MICROSOFT SQL SERVER IS CONFIGURATION OVERRIDE File defines overrides for SSIS parameters and variables. Each definition consists of name and value pair(e.g. param_name=param_value_verride). Each name should be prefixed with NAMESPACE. For example: $Project::project_parameter_1=global_override_1 $Package::package_parameter_1=global_override_2 User::user_variable_1=global_override_3 System::system_variable_1=global_override_4 Configuration pair can be set on ROOT(file beginning) or separated by CONTEXT([Project:project_name.]package_name[.task_name]). For example: $Project::project_parameter_1=global_override_1 // ROOT override [PackageName] $Project::project_parameter_1=global_override_2 // package specific overrride [PackageName.TaskName] User::task_variable_1=global_override_3 // task specific override For multi-project import CONTEXT requires Project prefix. For example: $Project::project_parameter_1=global_override_1 // ROOT, all projects override [Project:Project_1] $Project::project_parameter_1=global_override_2 // project "Project_1" specific overrride [Project:Project_1.PackageName.TaskName] $Project::project_parameter_1=global_override_3 // project "Project_1" package and task specific overrride [Project:Project_2.PackageName] $Project::project_parameter_1=global_override_4 // project "Project_2" package specific overrride Consider using the file when SSIS employs variables (without reasonable default values) in SQL statements. It should help with understanding lineage through SQL statements. When the same variable is defined multiple times in a context, the latest definition is used. However, when the same variable is defined in [Package] and [Package.Task] contexts the definition in the higher level context, [Package.Task] is used. Variable names are case sensitive. The file overrides default variable values if any defined in SSIS. |
FILE |
|
|||||||||||||||||||||||||||
| Encoding | Specifies an encoding character set of the source file for 'Execute SQL Task' when property 'SQLSourceType' is set to 'File connection'. | ENUMERATED |
|
windows-1252 | ||||||||||||||||||||||||||
| Miscellaneous | INTRODUCTION Specify miscellaneous options starting with a dash and optionally followed by parameters, e.g. -connection.cast MyDatabase1="MICROSOFT SQL SERVER" Some options can be used multiple times if applicable, e.g. -connection.rename NewConnection1=OldConnection1 -connection.rename NewConnection2=OldConnection2; As the list of options can become a long string, it is possible to load it from a file which must be located in ${MODEL_BRIDGE_HOME}\data\MIMB\parameters and have the extension .txt. In such case, all options must be defined within that file as the only value of this parameter, e.g. ETL/Miscellaneous.txt JAVA ENVIRONMENT OPTIONS -java.memory <Java Memory's maximum size> (previously -m) 1G by default on 64bits JRE or as set in conf/conf.properties, e.g. -java.memory 8G -java.memory 8000M -java.parameters <Java Runtime Environment command line options> (previously -j) This option must be the last one in the Miscellaneous parameter as all the text after -java.parameters is passed "as is" to the JRE, e.g. -java.parameters -Dname=value -Xms1G The following option must be set when a proxy is used to access internet (this is critical to access https://repo.maven.apache.org/maven2/ and exceptionally a few other tool sites) in order to download the necessary third-party software libraries. Note: The majority of proxies are concerned with encrypting (HTTPS) the outside (of the company) traffic and trust the inside traffic that can access proxy over HTTP. In this case, an HTTPS request reaches the proxy over HTTP where the proxy HTTPS-encrypts it. -java.parameters -java.parameters -Dhttp.proxyHost=127.0.0.1 -Dhttp.proxyPort=3128 -Dhttp.proxyUser=user -Dhttp.proxyPassword=pass MODEL IMPORT OPTIONS -model.name <model name> Override the model name, e.g. -model.name "My Model Name" -prescript <script name> This option allows running a script before the bridge execution. The script must be located in the bin directory (or as specified with M_SCRIPT_PATH in conf/conf.properties), and have .bat or .sh extension. The script path must not include any parent directory symbol (..). The script should return exit code 0 to indicate success, or another value to indicate failure. For example: -prescript "script.bat arg1 arg2" -postscript <script name> This option allows running a script after successful execution of the bridge. The script must be located in the bin directory (or as specified with M_SCRIPT_PATH in conf/conf.properties), and have .bat or .sh extension. The script path must not include any parent directory symbol (..). The script should return exit code 0 to indicate success, or another value to indicate failure. For example: -postscript "script.bat arg1 arg2" -cache.clear Clears the cache before the import, and therefore will run a full import without incremental harvesting. If the model was not changed and the -cache.clear parameter is not used (incremental harvesting), then a new version will not be created. If the model was not changed and the -cache.clear parameter is set (full source import instead of incremental), then a new version will be created. -backup <directory> This option allows to save the bridge input metadata for further troubleshooting. The provided <directory> must be empty. The primary use of this option is for data store import bridges, in particular JDBC based database import bridges. Note that this option is not operational on some bridges including: - File based import bridges (as such input files can be used instead) - DI/BI repository import bridges (as the tool's repository native backup can be used instead) - Some API based import bridges (e.g. COM based) for technical reasons. DATA CONNECTION OPTIONS Data Connections are produced by the import bridges typically from ETL/DI and BI tools to refer to the source and target data stores they use. These data connections are then used by metadata management tools to connect them (metadata stitching) to their actual data stores (e.g. databases, file system, etc.) in order to produce the full end to end data flow lineage and impact analysis. The name of each data connection is unique by import model. The data connection names used within DI/BI design tools are used when possible, otherwise connection names are generated to be short but meaningful such as the database / schema name, the file system path, or Uniform Resource Identifier (URI). The following option allows to manipulate connections. These options replaces the legacy options -c, -cd, and -cs. -connection.cast ConnectionName=ConnectionType Casts a generic database connection (e.g. ODBC/JDBC) to a precise database type (e.g. ORACLE) for SQL Parsing, e.g. -connection.cast "My Database"="MICROSOFT SQL SERVER". The list of supported data store connection types includes: ACCESS APACHE CASSANDRA DB2/UDB DENODO GOOGLE BIGQUERY HIVE MYSQL NETEZZA ORACLE POSTGRESQL PRESTO REDSHIFT SALESFORCE SAP HANA SNOWFLAKE MICROSOFT SQL AZURE MICROSOFT SQL SERVER SYBASE SQL SERVER SYBASE AS ENTERPRISE TERADATA VECTORWISE HP VERTICA -connection.rename OldConnection=NewConnection Renames an existing connection to a new name, e.g. -connection.rename OldConnectionName=NewConnectionName Multiple existing database connections can be renamed and merged into one new database connection, e.g. -connection.rename MySchema1=MyDatabase -connection.rename MySchema2=MyDatabase -connection.split oldConnection.Schema1=newConnection Splits a database connection into one or multiple database connections. A single database connection can be split into one connection per schema, e.g. -connection.split MyDatabase All database connections can be split into one connection per schema, e.g. -connection.split * A database connection can be explicitly split creating a new database connection by appending a schema name to a database, e.g. -connection.split MyDatabase.schema1=MySchema1 -connection.map SourcePath=DestinationPath Maps a source path to destination path. This is useful for file system connections when different paths points to the same object (directory or file). On Hadoop, a process can write into a CSV file specified with the HDFS full path, but another process reads from a Hive table implemented (external) by the same file specified using a relative path with default file name and extension, e.g. -connection.map /user1/folder=hdfs://host:8020/users/user1/folder/file.csv On Linux, a given directory (or file) like /data can be referred to by multiple symbolic links like /users/john and /users/paul, e.g. -connection.map /data=/users/John -connection.map /data=/users/paul On Windows, a given directory like C:\data can be referred to by multiple network drives like M: and N:, e.g. -connection.map C:\data=M:\ -connection.map C:\data=N:\ -connection.casesensitive ConnectionName Overrides the default case insensitive matching rules for the object identifiers inside the specified connection, provided the detected type of the data store by itself supports this configuration (e.g. Microsoft SQL Server, MySql etc.), e.g. -connection.casesensitive "My Database" -connection.level AggregationLevel Specifies the aggregation level for the external connections, e.g.-connection.level catalog The list of the supported values: server catalog schema (default) MICROSOFT SQL SERVER IS DATABASE OPTIONS -c The limit of dtsx packages cache received from the server. This option affects limit if 'Browse Folder Filter' option is empty. By default the bridge imports all packages. -s Enable specifying mappings between Transformation Script inputs and outputs externally. In this case, the inputs go to a table in '_Script_' database and outputs come from a table in the database. One can specify mapping relationships between inputs and outputs by defining a mapping between their tables. By default the bridge interconnect all inputs to all outputs in Transformation Scripts. -connection.fullyqualifiedname Prefixes connection names with {$project_name}:{$package_name}: tags. Helps to distinguish connections with same name in different packages. -connection.catalogname <boolean> Controls #{$catalog_name} suffix in relation database connection names. -connection.catalogname false -environment <string> Specify used Environment in format "environment_folder\environment_name". Actual if environment variable used. -cd <string> Split or merge file system connections by a directory path. Useful to split a connection into two or more root folders, that can be stitched to two or more file stores. To split the connection 'orig_con' into two connections: 'a_con' based upon the 'a' folder and the rest remains in the orig_con connection: -cd a_con=orig_con:/a To split the connection 'orig_con' into two connections: 'a_con' based upon the 'root/a' folder: -cd a_con=orig_con:/root/a - Useful to merge several connections into one. To merge two connections 'C:' with a root folder 'R1' and 'B:' with a root folder 'R2' into one connection 'C:' with two root folders - 'R1' and 'R2': -cd C:\=B:\ |
STRING |
Bridge Mapping
Mapping information is not available