requires the tool to be installed to access its SDK.
|Tool Name||SQL Server Integration Services (SSIS)|
|Tool Version||11.0 (2012) to 14.0 (2017)|
|Tool Web Site||http://msdn2.microsoft.com/en-us/library/ms141026.aspx|
|Supported Methodology||[Data Integration] Multi-Model, Metadata Repository, ETL (Source and Target Data Stores, Transformation Lineage, Expression Parsing) via JDBC API|
|Remote Repository Browsing for Model Selection|
Tool: Microsoft SQL Server Integration Services (SSIS) version 11.0 (2012) to 14.0 (2017) via JDBC API
Metadata: [Data Integration] Multi-Model, Metadata Repository, ETL (Source and Target Data Stores, Transformation Lineage, Expression Parsing)
Bridge: MicrosoftSqlServerRepositoryIsDb version 11.0.0
The bridge imports Packages from a corresponding SQL Server SSIS Catalog using a JDBC connection.
|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.
|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 name of the 'filter' folders in the SQL Server Integration Service catalog. Use this parameter if you need to limit the scope of repository structure browsing. If specifified, the bridge will only look in these folders for metadata browser.||REPOSITORY_SUBSET|
|Packages||SQL Server Integration Service package names to be processing.||REPOSITORY_SUBSET||Mandatory|
|Variable values file||File defines values for SSIS variables. Variables are grouped by their package and task context, and prefixed with namespace:
Consider using the file when SSIS employs variables (without reasonable default values) in SQL statements. It should help with understanding lineage through SQL statements.
The file supports SSIS 2005, 2008 and 2012 variables. It does not support SSIS 2012 parameters.
Use the [Package] context to define variables for all tasks in the Package.
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.
|Encoding||Specifies an encoding character set of the source file for 'Execute SQL Task' when property 'SQLSourceType' is set to 'File connection'.||ENUMERATED||
|Miscellaneous||Specify miscellaneous options identified with a -option followed by a value if required:
-m <Java Memory's maximum size>
1G by default on 64bits JRE or as set in conf/conf.properties, e.g.
-j <Java Runtime Environment command line options>
This option must be the last one in the Miscellaneous parameter as all the text after -j is passed "as is" to the JRE, e.g.
-j -Dname=value -Xms1G
-jre <Java Runtime Environment full path name>
It can be an absolute path to javaw.exe on Windows or a link/script path on Linux, e.g.
-jre "c:\Program Files\Java\jre1.8.0_211\bin\javaw.exe"
-v <Environment variable value>
None by default, e.g.
-v var1=value1 -v var2="value2 with spaces"
-model.name <model name>
Override the model name, e.g.
-model.name "My Model Name"
-prescript <script name>
The script must be located in the bin directory, 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.
MICROSOFT SQL SERVER IS DATABASE OPTIONS
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.
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.
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:
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':
Mapping information is not available