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|
Import tool: Microsoft SQL Server Integration Services (SSIS) 11.0 (2012) to 14.0 (2017) (http://msdn2.microsoft.com/en-us/library/ms141026.aspx)
Import interface: [Data Integration] Multi-Model, Metadata Repository, ETL (Source and Target Data Stores, Transformation Lineage, Expression Parsing) via JDBC API from Microsoft SQL Server Integration Services (SSIS) (Repository Database)
Import bridge: 'MicrosoftSqlServerRepositoryIsDb' 10.1.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.||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 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 -letter and value.
For example, -l -c -m 4G -j -Dname=value -Xms1G
-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.
-v set environment variable(s) (e.g. -v var1=value -v var2='value with spaces').
-m the maximum Java memory size whole number (e.g. -m 4G or -m 2500M ).
-cd: split or merge file system connections by a directory path.
For example, a connection can have two root folders, a and b. When you imported separate File stores for each root folder you would want to split the connection into two connections that can be resolved using these File stores. It can be achieved with option:
requesting to create 'a_con' connection and move the 'a' folder to it from the 'orig_con' connection. The result will have a_con and orig_con connections. The orig_con connection will have the folder branch 'b' that is left over after splinting the folder branch 'a' out.
Here is a little bit more complex example:
-cd a_con=orig_con:/root/a - create 'a_con' connection for the 'root/a' folder branch in the 'a_con' connection.
You can use the option to merge several connections into one. For example, when you have two file stores C:\a and B:\b you can merge them with the option:
that will move all folders from B:\ connection to C:\ that will end up with a and b root folders.
-j the last option that is followed by the java command line options (e.g. -j -Dname=value -Xms1G).
Mapping information is not available