|SQL Server Integration Services (SSIS)
|9.0 (2005) to 15x (2019)
|Tool Web Site
|[Data Integration] Multi-Model, Metadata Repository, ETL (Source and Target Data Stores, Transformation Lineage, Expression Parsing) via .Net API
Tool: Microsoft / SQL Server Integration Services (SSIS) version 9.0 (2005) to 15x (2019) via .Net API
Metadata: [Data Integration] Multi-Model, Metadata Repository, ETL (Source and Target Data Stores, Transformation Lineage, Expression Parsing)
Component: MicrosoftSqlServerRepositoryIs version 11.2.0
The bridge imports SSIS Packages from a corresponding SQL Server Repository using the SQL Server SDK APIs.
In order for this bridge to connect to the SQL Server Repository and import, it is necessary to ensure that the SQL Server Client Components are installed properly and corresponding services are running locally or established in your local network. The bridge uses Windows Authentication to connect to Integration Services. Please be sure the application is logged into Windows Domain as a 'User', which has appropriate rights to the objects you wish to import.
FREQUENTLY ASKED QUESTIONS
Q: Is it possible to disable case sensitivity for column names in SSIS packages?
A: ETL bridges import all features "AS IS" depending on the database type and its rules. The Database bridge sets case sensitive flag if needed and the stitcher is capable of stitching, even if names are in different cases.
Refer to the current general known limitations at http://metaintegration.com/Products/MIMB/MIMBKnownLimitations.html or bundled in Documentation/ReadMe/MIMBKnownLimitations.html
Provide a troubleshooting package with debug log. Debug log can be set in the UI or in conf/conf.properties with MIR_LOG_LEVEL=6
|SQL Server version
|Specifies the version of SQL Server.
|Host name or IP address where SQL Server IS is running.
|SQL Server Integration Service Project name to be processing.
|The value of the password for the protected package.
|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.
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.
|Meta Integration Repository (MIR)
(based on the OMG CWM standard)
|"Microsoft SQL Server Integration Services (SSIS) (Repository Server)"
|Connection or Trainsformation Output link
|Input/Output column lineageId link