Ataccama ONE Agentic ONE Desktop ONE DQ&C ONE MDM ONE RDM ONE Runtime Server
latest (17.1.0) 17.0.0 16.3.x 16.2.0 16.1.0 16.0.0 15.4.0 15.3.0 15.2.0 15.1.0 14.5.x 13.9.x 13.8.x 13.7.x 13.6.x 13.5.0 13.4.x 13.3.x 13.2.x
Downloads

Supported Technologies

Lineage connectors

Connection to lineage sources is separate from Data Catalog sources described in Connect to a Source.

Lineage connectors for individual scan plans are set up directly in the plan definition and are only supported in the scope described here.

Technology Supported scope Connector type Authentication

Azure Data Factory

Design-time lineage for:

  • Factories

  • Linked services

  • Pipelines

  • Datasets

  • Dataflows

API integration using the Microsoft Azure SDK

Azure Service Principal

AWS Glue

Runtime lineage for:

  • Spark-based AWS Glue jobs

Using OpenLineage.

BigQuery

Runtime lineage for:

  • DML statements

  • Views

  • Materialized views

JDBC

Service Account Key

Databricks

Databricks Unity Catalog runtime lineage

JDBC and Unity Catalog REST API

Personal Access Token (PAT) or Microsoft Entra ID (service principal)

File folder extraction is also supported.

dbt

Design-time lineage for the underlying database technology scanner. See the specific database technology scanner to determine the supported scope.

API

Service Account Token

File folder extraction is also supported.

Denodo

Design-time lineage for:

  • Virtual databases

  • Views (base and derived) and columns

  • Data sources

  • Derived view VQL and JDBC base-view wrapper SQL

JDBC

Username and password

Dremio

Design-time lineage for:

  • Views

JDBC

Username and password

MS SQL Server/Azure Synapse

Design-time lineage for:

  • DML statements

  • Views

  • Materialized views

  • Stored procedures

  • Temporary tables

JDBC

SQL Server Authentication using SQL login and password

OpenLineage

Runtime lineage. The scope depends on the producer. See the relevant documentation.

API

Oracle

Design-time lineage for:

  • DML statements

  • Views

  • Materialized views

  • PL/SQL procedures

JDBC

Username and password

SAP HANA

  • Views (design-time)

  • Tables and synonyms (metadata)

JDBC

Username and password

PowerBI

Design-time lineage for:

  • PowerBI cloud version

  • Workspaces

  • Datasets

  • Dataflows (Gen1)

  • Reports

  • Dashboards

For limitations on specific PowerQuery constructs and sources, see the scanner documentation.

REST API

OAuth 2.0 Client Credentials Flow (Service Principal)

Snowflake

Runtime lineage for:

  • DML statements

  • Views

  • Materialized views

  • Dynamic tables

  • External stages

  • Snowpipe

  • Streams

JDBC

Key pair authentication

SSIS

Design-time lineage for:

  • Folders

  • Projects

  • Packages and connection management files

JDBC

Username and password

Tableau

Design-time lineage for:

  • Both cloud and on-premise versions

  • Projects

  • Workbooks

  • Sheets

  • Dashboards

REST API and Metadata API (GraphQL)

Username and Personal Access Token (PAT)

Third-party lineage integrations

The following integrations bring lineage into ONE from external tools that perform the extraction themselves. Unlike other connectors listed here, ONE does not connect to the source system directly; instead, it imports lineage produced by the third-party tool.

Technology Supported scope Integration type Authentication

Rocket Software

Lineage produced by Rocket Software scanners and relayed to ONE through the Ataccama Rocket gateway.

Supported only on Windows, using WSL and a Linux-capable container manager (Docker or Podman).

Gateway relay between Ataccama and Rocket Software scanners

Handled by the Rocket Software installation

Safyr (Silwood)

Lineage for enterprise application metadata, such as SAP, Oracle E-Business Suite, and Salesforce, exported by Silwood Safyr as JSON.

ONE reads the exports from an Amazon S3 bucket. Optionally creates catalog items when the source is mapped to a SAP Safyr connection during import.

File-based import from Amazon S3 (read-only)

IAM role (assume role) or access key

Was this page useful?