Ataccama ONE Agentic ONE Desktop ONE DQ&C ONE MDM ONE RDM ONE Runtime Server
Downloads

MS SSIS Connection

This article describes how to connect to Microsoft SQL Server Integration Services (SSIS) for lineage extraction.

See also MS SSIS Lineage Scanner.

Availability

Data processing & catalog Edge processing Lineage Exceptions

✗

✗

✔

None

Prerequisites

  • Review how sources and connections work.

  • Create a source to add this connection to.

  • Make sure you have SSIS 2012 or later, with projects deployed to the SSIS catalog (SSISDB). The connection targets the SSISDB catalog database on your SQL Server or Azure SQL Database instance.

Add a connection

  1. Go to [your source] > Connections and select Add Connection.

  2. In Connection type, select SSIS.

  3. Fill in the following:

    • Name: A meaningful name for your connection. Used to indicate the location of catalog items.

    • Description (Optional): A short description of the connection.

    • Secret management service (Optional): The secret management service used to retrieve connection credentials at runtime. Available only if a secret management service is configured. See Secret Management Service.

    • JDBC: A JDBC connection string pointing to the SQL Server instance that hosts the SSISDB catalog database. See JDBC connection string format.

JDBC connection string format

The expected syntax is as follows:

Username and password authentication
jdbc:sqlserver://server_name:1433;encrypt=true;trustServerCertificate=false

For Azure SQL Database, use the full domain: server_name.database.windows.net.

The scanner always connects to the SSISDB database, so you don’t need to specify the database in the connection string. If you do, it must be SSISDB.

Add credentials

Only Username and password authentication (SQL Server Authentication) is currently supported.

The account used for metadata extraction needs specific permissions. See SSIS permissions.

Always use the dedicated credential fields for authentication details such as passwords, secrets, and tokens. This ensures credentials are handled with the appropriate level of protection and reliably preserved across environments.

To keep credentials in your existing infrastructure and have ONE retrieve them at runtime, configure a secret management service instead. See Secret Management Service.

One set of credentials must be defined as default for each connection. Otherwise, DQ evaluation fails and previewing data in the catalog is not possible.

  1. Select Add Credentials.

  2. Fill in the following:

    • Name: Provide a clear name for this set of credentials.

    • Description (Optional): Explain what the credentials are used for or provide other useful information.

    • Username: The SQL Server login.

    • Password: The password for the SQL Server login.

  3. To use this set of credentials by default when connecting to the data source, select Assign as default.

Next steps

Test and save your connection to complete setup.

Was this page useful?