Connection configuration - Precisely Data Integrity Suite

Data Integrity Suite

Product

Spatial_Analytics

Data_Integration

Data_Enrichment

Data_Governance

Precisely_Data_Integrity_Suite

geo_addressing_1

Data_Observability

Data_Quality

dis_core_foundation

Services

Spatial Analytics

Data Integration

Data Enrichment

Data Governance

Geo Addressing

Data Observability

Data Quality

Core Foundation

ft:title

Data Integrity Suite

ft:locale

en-US

PublicationType

pt_product_guide

copyrightfirst

2000

copyrightlast

2026

This section provides you the details on various fields required to configure Snowflake in Data Integrity Suite.

Field	Description
Name	Specifies the name of data connection. This is a mandatory field. Example: SalesDataConnection
Description	Allows you to describe the purpose of this data connection. Example: Connection to the sales data warehouse for quarterly reporting.
Agent to access data	Select the agent from the dropdown that connects to the database. It helps securely access data from your network.
Account	The unique identifier for your Snowflake account. It can be your organization name or a specific account ID needed to connect to Snowflake. This field is mandatory, and only the format `<orgname>-<account_name>` is valid in the Data Integrity Suite. Example: Corp-data_warehouse Note: When providing the information to the account field, ensure to exclude `https:// or http://` from the URL.
Role	Specifies the Snowflake role for the connection, defining access to databases, schemas, and tables. It must have read and write permissions to work with the Data Integrity Suite. This is a mandatory field. Note: When integrating Data Integrity Suite with Snowflake, read and write permissions are required only if the workspace includes Quality. If used solely for data cataloging, these permissions are not needed.
Warehouse	Specifies the name of the Snowflake warehouse to be used for query execution. This is a mandatory field. Example: compute_wh For recommendations on warehouse sizing for Data Quality rules, refer to Recommendation for warehouse sizing for Snowflake datasource
Database	Specifies the name of database to connect to on the designated host server. This is a mandatory field. Example: sales_db
Operational Lineage	Operational Lineage: Toggle to enable operational lineage harvesting on this connection. When enabled, the Data Catalog service harvests fresh lineage from your Snowflake environment on each catalog run. This requires Advanced Connectivity Bundle (ACB) entitlement and Snowflake Enterprise Edition or higher with Access History enabled. For more information, see Operational lineage harvesting overview. Lineage Mode: Select your harvesting mode (visible only when runtime lineage is enabled): Harvest Latest Available Lineage: Retrieves all lineage the platform currently holds with no time filter. This is the default option. Specify Lineage Window: Limits lineage harvesting to a custom number of days to control query costs. Lineage Window (Days): Enter the number of days to look back (visible only when "Specify Runtime Lineage Window" is selected). Minimum value is 1 day. Suggested values: 7, 30, 60, 90, 180, 365.
Advanced Options	Allows you to set the connector log level and define additional parameters for the Snowflake connection. Operational lineage query timeout: Runtime lineage harvesting queries have a default timeout of 3600 seconds (1 hour). If needed, you can override this value using a debug parameter: Key: `lineageQueryTimeoutSeconds` Value: Timeout duration in seconds. For example, specify `7200` to set the timeout to 2 hours.

Note: During configuration, the Data Integrity Suite creates an internal stage in Snowflake and stores java files for Data Quality pipeline execution.