Supported connectors for lineage import
You can connect to many data sources from which you can import lineage metadata.
Requirements
The IBM watsonx.data intelligence service is required.
Users must be authorized to access data sources with the appropriate privileges. For privilege requirements for each data source, see dedicated topics which are listed in the Supported data sources section.
How to create a connection
For details about how to add a connection to a selected data source in a project, see Adding connections to data sources in a project.
Supported data sources for lineage import, asset import, and Manta agent requirements
The following table lists supported data sources for lineage metadata import, and asset metadata import. Only the data sources listed in this table can be used for lineage and asset import. For data sources that support remote connection through a Manta agent, the minimum required agent version is shown. A dash (—) indicates that agent connection is not supported for that data source.
For details about asset import, see Importing assets with data lineage connections.
| Supported data source | Lineage import | Asset import (data governance connector) | Asset import (data lineage connector) | Minimum agent version (if applicable) |
|---|---|---|---|---|
| Amazon RDS for Oracle | ✓ | ✓ | — | — |
| Amazon RDS for PostgreSQL | ✓ | ✓ | — | 1.2.0-saas |
| Amazon Redshift | ✓ | ✓ | — | 1.2.0-saas |
| Apache Hive | ✓ | ✓ | — | 1.2.0-saas |
| Google BigQuery | ✓ | ✓ | — | 1.2.0-saas |
| Greenplum | ✓ | ✓ | — | 1.2.0-saas |
| IBM Cloud Databases for PostgreSQL | ✓ | ✓ | — | 1.2.0-saas |
| IBM Cognos Analytics | ✓ | ✓ | — | 1.2.0-saas |
| IBM DataStage for Cloud Pak for Data | ✓ | ✓ | — | 1.2.0-saas |
| IBM Db2 | ✓ | ✓ | — | 1.2.0-saas |
| IBM Db2 for z/OS | ✓ | ✓ | — | 1.2.0-saas |
| IBM Db2 on Cloud | ✓ | ✓ | — | 1.2.0-saas |
| Informatica PowerCenter | ✓ | — | ✓ | 1.2.0-saas |
| InfoSphere DataStage | ✓ | — | ✓ | — |
| Microsoft Azure Databricks | ✓ | ✓ | — | 1.2.0-saas |
| Microsoft Azure SQL Database | ✓ | ✓ | — | — |
| Microsoft Power BI (Azure) | ✓ | — | ✓ | 1.2.0-saas |
| Microsoft Power BI Report Server (Microsoft Power BI Desktop) | ✓ | ✓ | — | 1.2.0-saas |
| Microsoft SQL Server | ✓ | ✓ | — | — |
| Microsoft SQL Server Integration Services (SSIS) | ✓ | — | ✓ | 1.2.0-saas |
| MicroStrategy | ✓ | — | ✓ | — |
| OpenLineage | ✓ | ✓ | — | — |
| Oracle | ✓ | ✓ | — | — |
| PostgreSQL | ✓ | ✓ | — | 1.2.0-saas |
| Qlik Sense | ✓ | — | ✓ | 1.2.0-saas |
| SAP BusinessObjects | ✓ | — | — | 1.2.0-saas |
| Snowflake | ✓ | ✓ | — | — |
| Statistical Analysis System (SAS) | ✓ | — | ✓ | — |
| Tableau | ✓ | ✓ | — | 1.2.0-saas |
| Talend | ✓ | — | ✓ | — |
| Teradata | ✓ | ✓ | — | — |
| YugabyteDB | ✓ | ✓ | — | 1.2.0-saas |
Connecting to data sources with IBM Satellite
When you connect to a data source by using a connection that is configured as private with IBM Satellite, you must use a Manta external agent to import lineage metadata.
The same connection configuration can be used by both the Satellite connector and the Manta external agent, provided that the data source hostname and port are reachable from both components. This typically requires that the Satellite connector and the Manta external agent are deployed in the same network segment, or in network segments with equivalent access to the data source.
For details, see Configuring agents for lineage metadata import and Satellite Connector overview.