SQL Server Integration Services: Supported transformation details
Collibra Data Lineage collects metadata from SSIS packages (.dtsx), connection manager files (.conmgr), and parameter files (.params), if applicable, to build technical lineage.
Supported connection managers
Collibra Data Lineage parses the connection strings in SSIS connection managers to identify source and target systems. The following connection types are supported:
|
Connection type |
How it appears in Collibra |
|---|---|
| Microsoft access (.mdb .accdb) |
Maps the file name to the database name. If the value cannot be resolved from the connection string, the default value |
| OLEDB, ODBC, and ADO | Maps the user ID to the schema name. If the value cannot be resolved from the connection string, the default value DEFAULT is used. |
If your technical lineage graph displays DEFAULT for a database or schema name, you can manually map these values to the correct assets by using the Source Configuration field in the Technical Lineage for SQL Server Integration Services (SSIS) capability.
Supported transformations and component types
Collibra Data Lineage supports the following non-exhaustive list of transformations and component types in SQL Server Integration Services:
|
Supported transformations |
Supported component types |
|---|---|
|
|
- Collibra Data Lineage supports SQL, but cannot parse other languages or scripts, for example SHELL and BAT scripts.
- SQL statements from Excel are not supported.
- Collibra Data Lineage does not create lineage for disabled executables.
- Collibra Data Lineage ignores the
CONTEXTkeyword in SQL Server queries when parsing metadata from Denodo sources.