> For the complete documentation index, see [llms.txt](https://docs.collibra.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.collibra.com/data-quality-self-hosted/core-concepts/explorer/processing-methods/pushdown-processing/setting-up-a-pushdown-connection.md). # Setting up a Pushdown connection Pushdown processing is currently available for the data sources listed within the tabbed section below. Click a tab to see the Pushdown setup information for an available data source. {% tabs %} {% tab title="Databricks" %} This section shows you how to set up [Pushdown](/data-quality-self-hosted/core-concepts/explorer/processing-methods/pushdown-processing.md) for a [Databricks connection](/data-quality-self-hosted/connections/supported-connections/supported-jdbc-data-sources/connecting-to-databricks.md). ## Requirements ### In Collibra DQ You have: * Admin permissions to set up the Databricks connection template and enable Pushdown. * Databricks JDBC driver version [2.6.32+](https://www.databricks.com/spark/jdbc-drivers-download) for [Standalone](/data-quality-self-hosted/installation/installing-data-quality-observability-self-hosted-on-self-hosted-spark-standalone.md) deployments of Collibra DQ.

You do not need to install the Databricks JDBC driver for Installing Data Quality & Observability (self-hosted) on self-hosted Kubernetes deployments of Collibra DQ because it is already included in the installation package.

### In Databricks You have: * A [personal access token](https://docs.gcp.databricks.com/administration-guide/access-control/tokens.html) to establish a connection between Collibra DQ and Databricks. * A Databricks workspace admin [SQL warehouse](https://docs.gcp.databricks.com/sql/admin/create-sql-warehouse.html) that is set up in your Databricks workspace.

Your SQL warehouse can use either the Hive Metastore or the Delta Lake Unity Catalog for metadata management. Note that when you run Pushdown jobs on tables within the Hive Metastore without adding Unity Catalog to the connection string, Explorer displays all tables available in your Databricks workspace. However, only the tables that are viewable from Databricks under the Hive Metastore can be accessed to run Pushdown jobs on them. We recommend adding a Unity Catalog to your connection URL to run Pushdown jobs on all tables within your Databricks workspace.

* Read access to the tables on which you plan to run DQ scans. * A Databricks workspace admin can enable the Can Read permission in the Permission Settings section of your Databricks workspace. ## Configuring Pushdown for Databricks The following steps show you how to set up the Databricks connection template with Pushdown enabled. ### Setting up the Databricks connection template The following steps show you how to set up the Databricks connection template with Pushdown enabled. {% stepper %} {% step %} On the main menu, click , and then click **Connections**. {% endstep %} {% step %} Click the Databricks tile, then enter the required information. | Required | Property | Type | Description | | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------ | --------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | Yes | Name | String | The unique name of your Databricks connection. | | Yes | Connection URL | String |

The base connection string, for example, jdbc:databricks\://\.cloud.databricks.com/?db=DATABRICKS\_SAMPLE\_DATA;ConnCatalog=\

ConnCatalog=\ is required if you use Unity Catalog for metadata management. However, it is not required if you use the Hive Metastore.

| | Yes | Port | Integer | The port number to establish a connection to the datasource. The default port is 0. | | Yes | Driver Name | String | The driver class name used for your connection, for example, `com.databricks.client.jdbc.Driver` | | No | Source Name | String | Not applicable. | | No | Target Agent | Option |

The Agent used to submit your DQ Job.

You do not need to select an option because Pushdown Jobs do not require an Agent to submit them to the data warehouse.

| | Yes | Auth Type | Option | The method to authenticate your connection. For more information on authentication methods for Databricks connections, go to the [Databricks documentation](/data-quality-self-hosted/connections/supported-connections/supported-jdbc-data-sources/connecting-to-databricks.md). | | Yes | Pushdown | Option |

Switches Pushdown processing on or off.

Select the checkbox option to turn on Pushdown for your Databricks connection.

You must select this option for Pushdown to function.

| | No | Archive Break Records | Option | Allows you to write break records directly to a Databricks database or schema. | | Yes | Archive Break Records Location | String | The break records archive location within Databricks. If you do not specify a location, then Collibra DQ uses PUBLIC by default. | | Yes | Driver Location | File path | A file path that designates the name and location of the driver. | | No | Driver Properties | String | Optional. The configurable driver properties for your connection. | | {% endstep %} | | | | {% step %} Click **Save**. {% endstep %} {% endstepper %} ## What's next You can now [create a Pushdown job](/data-quality-self-hosted/core-concepts/explorer/create-a-dq-job.md) on your Databricks connection. {% endtab %} {% tab title="Snowflake" %} This section shows you how to set up Pushdown for a [Snowflake connection](/data-quality-self-hosted/connections/supported-connections/supported-jdbc-data-sources/connecting-to-snowflake.md). * [Running Snowflake setup scripts](#running-snowflake-setup-scripts) * [Setting up the Snowflake Connection template](#setting-up-the-snowflake-connection-template) ## Running Snowflake setup scripts {% hint style="info" %} The following scripts are examples only. Be sure to modify them for your environment. {% endhint %}
StepDetails
1Open a Snowflake worksheet.
2

Update the following session variables:

set dq_username='SERVICE_ACCOUNT_USER';
set dq_password='SERVICE_ACCOUNT_PASSWORD';
set dq_warehouse_name='COLLIBRA_DQ_WH';
set dq_warehouse_size='XSMALL';
set user_database='TARGET_DB';
set dq_role_name='COLLIBRA_DQ_ROLE';

dq_password must be uppercase.

3

Run as an admin user.

USE ROLE ACCOUNTADMIN;

If the usage of ACCOUNTADMIN is restricted in your organization, you may use USERADMIN, SECURITYADMIN, and SYSADMIN instead.

4

Create a user and role for Collibra DQ.

CREATE ROLE IF NOT EXISTS identifier($dq_role_name);
CREATE USER IF NOT EXISTS identifier($dq_username) PASSWORD=$dq_password DEFAULT_ROLE=$dq_role_name;
GRANT ROLE identifier($dq_role_name) TO USER identifier($dq_username);

Customers may manage users and roles according to their own policies and procedures.

5

Create a virtual warehouse to run Collibra DQ. The virtual warehouse is referenced in the connection URL to direct DQ traffic to it.

CREATE WAREHOUSE IF NOT EXISTS identifier($dq_warehouse_name) WAREHOUSE_SIZE=$dq_warehouse_size INITIALLY_SUSPENDED=TRUE
AUTO_SUSPEND = 5 AUTO_RESUME = TRUE;

Customers may manage warehouses according to their own policies and procedures.

6

Assign privileges to the Collibra DQ warehouse.

GRANT OPERATE, USAGE, MONITOR ON WAREHOUSE identifier($dq_warehouse_name) TO ROLE identifier($dq_role_name);

Customers may manage warehouses according to their own policies and procedures.

7

Assign metadata access to your Collibra DQ role.

GRANT USAGE,MONITOR on DATABASE identifier($user_database) to identifier($dq_role_name);
GRANT USAGE,MONITOR ON ALL SCHEMAS IN DATABASE identifier($user_database) to identifier($dq_role_name);

Customers may manage databases and schemas according to their own policies and procedures.

8

Update the session variable user_database and grant read access to objects in the user database. Run this portion for each target database within which you want to run DQ checks.

USE DATABASE identifier($user_database);
GRANT SELECT ON ALL TABLES IN DATABASE identifier($user_database) TO ROLE identifier($dq_role_name);
GRANT SELECT ON ALL VIEWS IN DATABASE identifier($user_database) TO ROLE identifier($dq_role_name);
GRANT SELECT ON ALL EXTERNAL TABLES IN DATABASE identifier($user_database) TO ROLE identifier($dq_role_name);
GRANT SELECT ON ALL STREAMS IN DATABASE identifier($user_database) TO ROLE identifier($dq_role_name);
                                ​
GRANT SELECT ON FUTURE TABLES IN DATABASE identifier($user_database) TO ROLE identifier($dq_role_name);
GRANT SELECT ON FUTURE VIEWS IN DATABASE identifier($user_database) TO ROLE identifier($dq_role_name);
GRANT SELECT ON FUTURE EXTERNAL TABLES IN DATABASE identifier($user_database) TO ROLE identifier($dq_role_name);
GRANT SELECT ON FUTURE STREAMS IN DATABASE identifier($user_database) TO ROLE identifier($dq_role_name);
{% hint style="info" %} For information on configuring archiving, go to [Archiving break records from Pushdown jobs](/data-quality-self-hosted/core-concepts/findings/break-records-and-link-ids/archiving-break-records-from-pushdown-jobs.md). {% endhint %} ## Setting up the Snowflake Connection template The following steps show you how to set up the Snowflake connection template with Pushdown enabled. {% stepper %} {% step %} On the main menu, click , and then click **Connections**. {% endstep %} {% step %} Click the Snowflake tile, then enter the required information.
RequiredPropertyTypeDescription
YesNameTextThe unique name of your Snowflake connection.
YesConnection URLStringThe base connection string, for example, jdbc:snowflake://<account>.snowflakecomputing.com/?db=SNOWFLAKE_SAMPLE_DATA&warehouse=COLLIBRA_DQ_WH
YesPortIntegerThe port number to establish a connection to the datasource.
YesDriver NameTextThe driver class name used for your connection, for example, com.snowflake.client.jdbc.SnowflakeDriver
NoSource NameStringN/A
NoTarget AgentOption

The Agent used to submit your DQ Job.

You do not need to select an option because Pushdown Jobs do not require an Agent to submit them to the data warehouse.

YesAuth TypeOptionThe method to authenticate your connection. See the Snowflake documentation for more information about authentication methods for Snowflake connections.
YesPushdownCheckbox

Switches Pushdown processing on or off.

Select the checkbox option to turn on Pushdown for your Snowflake connection.

You must select this option for Pushdown to function.

NoArchive Break RecordsOption

Allows you to write break records directly to a Snowflake database or schema.

Ensure that you have the necessary privileges to write break records to Snowflake.

YesDriver LocationFile pathA file path which designates the name and location of the driver.
YesDriver PropertiesString

The configurable driver properties for your connection. Add the following driver property:

CLIENT_METADATA_REQUEST_USE_CONNECTION_CTX=TRUE
Show example The following image shows an example of a Snowflake connection with Pushdown selected. ![screenshot of a sample snowflake pushdown connection with 'pushdown' and 'driver properties' highlighted](https://4121921244-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FWCrP7Albs8DfJjIQxUxw%2Fuploads%2Fgit-blob-97eb25ab5972e4f3867226334d6c80e2cf097779%2Fdq-connections-snowflake-pushdown.png?alt=media)
{% endstep %} {% step %} Click **Save**. {% endstep %} {% endstepper %} ## Known limitations * There is a limitation where Snowflake Pushdown jobs with queries containing REGEXP\_REPLACE fail because Snowflake does not currently support arguments with collation specifications. There are two known workarounds: * Make a clone of the table that is synced in Snowflake and has no collation set. * Use Pullup mode instead of Pushdown to avoid this Snowflake limitation. ## What's next You can now [create a Pushdown job](/data-quality-self-hosted/core-concepts/explorer/create-a-dq-job.md) on your Snowflake connection. To run a Snowflake Pushdown job, you need to opt in when setting up your Snowflake connection. Select the Pushdown option in the Connection template to turn on Pushdown capabilities. {% endtab %} {% tab title="BigQuery" %} This section shows you how to set up [Pushdown](/data-quality-self-hosted/core-concepts/explorer/processing-methods/pushdown-processing.md) for a [BigQuery connection](/data-quality-self-hosted/connections/supported-connections/supported-jdbc-data-sources/connecting-to-google-bigquery.md). ## Requirements ### In Collibra DQ * You have admin permissions (`ROLE_ADMIN`) to set up the BigQuery connection template and enable Pushdown. * You have BigQuery JDBC driver version 1.3.2.1003 for [Standalone](/data-quality-self-hosted/installation/installing-data-quality-observability-self-hosted-on-self-hosted-spark-standalone.md) deployments of Collibra DQ.

You do not need to install the BigQuery JDBC driver for Installing Data Quality & Observability (self-hosted) on self-hosted Kubernetes deployments of Collibra DQ because it is already included in the installation package.

### In BigQuery * You have `Viewer` (`roles/viewer`) permissions. * You have `Reader` access to BigQuery dataset tables. * You have `Writer` access to materialized view datasets. ## Configuring Pushdown for BigQuery The following steps show you how to set up the BigQuery connection template with Pushdown enabled. ### Setting up the BigQuery connection template The following steps show you how to set up the BigQuery connection template with Pushdown enabled. {% stepper %} {% step %} On the main menu, click , and then click **Connections**. {% endstep %} {% step %} Click the BigQuery tile, then enter the required information. | Required | Property | Type | Description | | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------ | --------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | | Yes | Name | String | The unique name of your BigQuery connection. | | Yes | Connection URL | String | The base connection string, for example, `jdbc:bigquery://https://www.googleapis.com/bigquery/v2:443;OAuthType=0;ProjectId=owl-hadoop-cdh;OAuthServiceAcctEmail=;TimeOut=3600` | | Yes | Port | Integer | The port number to establish a connection to the datasource. The default port is 443. | | Yes | Driver Name | String |

The driver class name used for your connection, for example, com.simba.googlebigquery.jdbc42.Driver

The cdata.jdbc.googlebigquery.GoogleBigQueryDriver does not support Pushdown.

| | No | Source Name | String | N/A | | No | Target Agent | Option |

The Agent used to submit your DQ Job.

You do not need to select an option because Pushdown jobs do not require an Agent to submit them to the data warehouse.

| | Yes | Auth Type | Option | The method to authenticate your connection. For more information on authentication methods for BigQuery connections, go to the [official BigQuery documentation](/data-quality-self-hosted/connections/supported-connections/supported-jdbc-data-sources/connecting-to-google-bigquery.md). | | Yes | Pushdown | Checkbox |

Switches Pushdown processing on or off.

Select the checkbox option to turn on Pushdown for your BigQuery connection.

You must select this option for Pushdown to function.

| | No | Archive Break Records | Option | Allows you to write break records directly to a BigQuery database or schema. | | Yes | Archive Break Records Location | String |

The break records archive location within BigQuery. If you do not specify a location, then Collibra DQ uses PUBLIC by default.

Archive Break Records Location is only available and required when the Archive Break Records option is selected.

| | Yes | Driver Location | File path | A file path that designates the name and location of the driver. For example, /opt/owl/drivers/bigquery | | No | Driver Properties | String | Optional. The configurable driver properties of your connection. | | {% endstep %} | | | | {% step %} Click **Save**. {% endstep %} {% endstepper %} ## Limitations Rule validation for BigQuery Pushdown connections is not supported. However, you can manually execute SQL queries from the BigQuery console on GCP as a possible workaround. ## What's next You can now [create a Pushdown job](/data-quality-self-hosted/core-concepts/explorer/create-a-dq-job.md) on your BigQuery connection. {% endtab %} {% tab title="Athena" %} This section shows you how to set up [Pushdown](/data-quality-self-hosted/core-concepts/explorer/processing-methods/pushdown-processing.md) for an [Amazon Athena connection](/data-quality-self-hosted/connections/supported-connections/supported-jdbc-data-sources/connecting-to-amazon-athena.md). ## Requirements ### In Collibra DQ * You have admin permissions (`ROLE_ADMIN`) to set up the Athena connection template and enable Pushdown. * You have Athena JDBC driver version 2.0.35.1000 for [Standalone](/data-quality-self-hosted/installation/installing-data-quality-observability-self-hosted-on-self-hosted-spark-standalone.md) deployments of Collibra DQ.

You do not need to install the Athena JDBC driver for Installing Data Quality & Observability (self-hosted) on self-hosted Kubernetes deployments of Collibra DQ because it is already included in the installation package.

### In Athena * You have `Read` access to your Glue Catalog and S3 query result bucket location. * You have `Write` access to your S3 query result bucket location. * You have `Read` access to the Athena workgroup. ## Configuring Pushdown for Athena The following steps show you how to set up the Athena connection template with Pushdown enabled. {% stepper %} {% step %} On the main menu, click , and then click **Connections**. {% endstep %} {% step %} Click the Athena tile, then enter the required information. | Required | Property | Type | Description | | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------- | --------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | Yes | Name | String | The unique name of your Athena connection. | | Yes | Connection URL | String | The base connection string, for example, `jdbc:awsathena://AwsRegion=${region};S3OutputLocation=s3://{output_location};MetadataRetrievalMethod=Query` | | Yes | Port | Integer | The port number to establish a connection to the datasource. The default port is 444. | | Yes | Driver Name | String |

The driver class name of your connection, for example, com.simba.athena.jdbc.Driver

The cdata.jdbc.amazonathena driver class does not support Pushdown.

| | No | Source Name | String | N/A | | No | Target Agent | Option |

The Agent used to submit your DQ Job.

You do not need to select an option because Pushdown jobs do not require an Agent to submit them to the data warehouse.

| | Yes | Auth Type | Option | The method to authenticate your connection. For more information on authentication methods for Athena connections, go to the [official Athena documentation](/data-quality-self-hosted/connections/supported-connections/supported-jdbc-data-sources/connecting-to-amazon-athena.md). | | Yes | Pushdown | Checkbox |

Switches Pushdown processing on or off.

Select the checkbox option to turn on Pushdown for your Athena connection.

You must select this option for Pushdown to function.

| | Yes | Driver Location | File path | A file path that designates the name and location of the driver. For example, /opt/owl/drivers/athena/ | | No | Driver Properties | String | Optional. The configurable driver properties of your connection. | | {% endstep %} | | | | {% step %} Click **Save**. {% endstep %} {% endstepper %} ## What's next You can now [create a Pushdown job](/data-quality-self-hosted/core-concepts/explorer/create-a-dq-job.md) on your Athena connection. ## Known limitations * Only the AdaptiveRules layer is available from the Add Layers step. {% endtab %} {% tab title="Redshift" %} This section shows you how to set up [Pushdown](/data-quality-self-hosted/core-concepts/explorer/processing-methods/pushdown-processing.md) for a [Redshift connection](/data-quality-self-hosted/connections/supported-connections/supported-jdbc-data-sources/connecting-to-amazon-redshift.md). ## Requirements ### In Collibra DQ * You have admin permissions (`ROLE_ADMIN`) to set up the Redshift connection template and enable Pushdown. * You have Redshift JDBC driver version 2.1.0.9 for [Standalone](/data-quality-self-hosted/installation/installing-data-quality-observability-self-hosted-on-self-hosted-spark-standalone.md) deployments of Collibra DQ.

You do not need to install the Redshift JDBC driver for Installing Data Quality & Observability (self-hosted) on self-hosted Kubernetes deployments of Collibra DQ because it is already included in the installation package.

### In Redshift * You have `READ` access on your Redshift database tables. * You have `USAGE` access on your Redshift schema. ## Configuring Pushdown for Redshift The following steps show you how to set up the Redshift connection template with Pushdown enabled. {% stepper %} {% step %} On the main menu, click , and then click **Connections**. {% endstep %} {% step %} Click the Redshift tile, then enter the required information. | Required | Property | Type | Description | | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------- | --------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | Yes | Name | String | The unique name of your Redshift connection. | | Yes | Connection URL | String | The base connection string, for example, `jdbc:redshift://:5439/dev` | | Yes | Port | Integer | The port number to establish a connection to the datasource. The default port is 5439. | | Yes | Driver Name | String | The driver class name used for your connection, for example, `com.amazon.redshift.jdbc42.Driver` | | No | Source Name | String | N/A | | No | Target Agent | Option |

The Agent used to submit your DQ Job.

You do not need to select an option because Pushdown jobs do not require an Agent to submit them to the data warehouse.

| | Yes | Auth Type | Option | The method to authenticate your connection. For more information on authentication methods for Redshift connections, go to the [official Redshift documentation](/data-quality-self-hosted/connections/supported-connections/supported-jdbc-data-sources/connecting-to-amazon-redshift.md). | | Yes | Pushdown | Checkbox |

Switches Pushdown processing on or off.

Select the checkbox option to turn on Pushdown for your Redshift connection.

You must select this option for Pushdown to function.

| | Yes | Driver Location | File path | A file path that designates the name and location of the driver. For example, /opt/owl/drivers/redshift/ | | No | Driver Properties | String | Optional. The configurable driver properties of your connection. | | {% endstep %} | | | | {% step %} Click **Save**. {% endstep %} {% endstepper %} ## What's next You can now [create a Pushdown job](/data-quality-self-hosted/core-concepts/explorer/create-a-dq-job.md) on your Redshift connection. ## Known limitations * Only the AdaptiveRules layer is available from the Add Layers step. {% endtab %} {% tab title="Trino" %} This section shows you how to set up [Pushdown](/data-quality-self-hosted/core-concepts/explorer/processing-methods/pushdown-processing.md) for a [Trino connection](/data-quality-self-hosted/connections/supported-connections/supported-jdbc-data-sources/connecting-to-trino.md). ## Requirements ### In Collibra DQ * You have admin permissions (`ROLE_ADMIN`) to set up the Trino connection template and enable Pushdown. * You have Trino JDBC driver version 405.0 for [Standalone](/data-quality-self-hosted/installation/installing-data-quality-observability-self-hosted-on-self-hosted-spark-standalone.md) deployments of Collibra DQ.

You do not need to install the Trino JDBC driver for Installing Data Quality & Observability (self-hosted) on self-hosted Kubernetes deployments of Collibra DQ because it is already included in the installation package.

### In Trino * You have Read access on your Trino database tables. ## Configuring Pushdown for Trino The following steps show you how to set up the Trino connection template with Pushdown enabled. {% stepper %} {% step %} On the main menu, click , and then click **Connections**. {% endstep %} {% step %} Click the Trino tile, then enter the required information. | Required | Property | Type | Description | | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------ | --------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | Yes | Name | String | The unique name of your Trino connection. | | Yes | Connection URL | String | The base connection string, for example, `jdbc:trino://${host}:443//&source=jdbc:presto` | | Yes | Port | Integer | The port number to establish a connection to the datasource. The default port is 8080. | | Yes | Driver Name | String | The driver class name used for your connection, for example, `io.trino.jdbc.TrinoDriver` | | No | Source Name | String | N/A | | No | Target Agent | Option |

The Agent used to submit your DQ Job.

You do not need to select an option because Pushdown jobs do not require an Agent to submit them to the data warehouse.

| | Yes | Auth Type | Option | The method to authenticate your connection. For more information on authentication methods for Trino connections, go to the [official Trino documentation](/data-quality-self-hosted/connections/supported-connections/supported-jdbc-data-sources/connecting-to-trino.md). | | Yes | Pushdown | Checkbox |

Switches Pushdown processing on or off.

Select the checkbox option to turn on Pushdown for your Trino connection.

You must select this option for Pushdown to function.

| | No | Archive Break Records | Option | Allows you to write break records directly to a Trino database or schema. | | Yes | Archive Break Records Location | String |

The break records archive location within Trino. If you do not specify a location, then Collibra DQ uses PUBLIC by default.

Archive Break Records Location is only available and required when the Archive Break Records option is selected.

| | Yes | Driver Location | File path | A file path that designates the name and location of the driver. For example, /opt/owl/drivers/trino | | No | Driver Properties | String | Optional. The configurable driver properties of your connection. | | {% endstep %} | | | | {% step %} Click **Save**. {% endstep %} {% endstepper %} ### Turning on Pushdown for Trino To ensure that Pushdown for Trino is appropriately configured, verify that PUSHDOWN\_JOB\_ENABLED is set to `TRUE` on the Application Config page of the Admin Console. {% stepper %} {% step %} On the main menu, click , and then click **Admin Console**. {% endstep %} {% step %} Click **Application Config** under the Configuration Settings section. {% hint style="success" %} If PUSHDOWN\_JOB\_ENABLED is already set to `TRUE`, you can skip this section. {% endhint %} {% endstep %} {% step %} If PUSHDOWN\_JOB\_ENABLED is set to `FALSE`, click the to the right of the Value column. {% endstep %} {% step %} In the Edit Configuration modal, enter `TRUE` into the Value input field. {% endstep %} {% step %} Click **Save**. {% endstep %} {% endstepper %} ## What's next You can now [create a Pushdown job](/data-quality-self-hosted/core-concepts/explorer/create-a-dq-job.md) on your Trino connection. {% endtab %} {% tab title="SQL Server" %} This section shows you how to set up [Pushdown](/data-quality-self-hosted/core-concepts/explorer/processing-methods/pushdown-processing.md) for a [SQL Server connection](/data-quality-self-hosted/connections/supported-connections/supported-jdbc-data-sources/connecting-to-sql-server.md). ## Requirements ### In Collibra DQ * You have admin permissions (`ROLE_ADMIN`) to set up the SQL Server connection template and enable Pushdown. * You have the SQL Server JDBC driver for [Standalone](/data-quality-self-hosted/installation/installing-data-quality-observability-self-hosted-on-self-hosted-spark-standalone.md) deployments of Collibra DQ.

You do not need to install the SQL Server JDBC driver for Installing Data Quality & Observability (self-hosted) on self-hosted Kubernetes deployments of Collibra DQ because it is already included in the installation package.

### In SQL Server * You have Read access on your SQL Server database tables. ## Configuring Pushdown for SQL Server The following steps show you how to set up the SQL Server connection template with Pushdown enabled. {% stepper %} {% step %} On the main menu, click , and then click **Connections**. {% endstep %} {% step %} Click the SQL Server tile, then enter the required information. | Required | Property | Type | Description | | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------ | --------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | | Yes | Name | String | The unique name of your SQL Server connection. | | Yes | Connection URL | String | The base connection string, for example, `jdbc:sqlserver://${host}:1433/databaseName=${dbName};encrypt=true;trustServerCertificate=true;` | | Yes | Port | Integer | The port number to establish a connection to the datasource. The default port is 1433. | | Yes | Driver Name | String | The driver class name used for your connection, for example, `com.microsoft.sqlserver.jdbc.SQLServerDriver` | | No | Source Name | String | N/A | | No | Target Agent | Option |

The Agent used to submit your DQ Job.

You do not need to select an option because Pushdown jobs do not require an Agent to submit them to the data warehouse.

| | Yes | Auth Type | Option | The method to authenticate your connection. For more information on authentication methods for SQL Server connections, go to the [official SQL Server documentation](/data-quality-self-hosted/connections/supported-connections/supported-jdbc-data-sources/connecting-to-sql-server.md). | | Yes | Pushdown | Checkbox |

Switches Pushdown processing on or off.

Select the checkbox option to turn on Pushdown for your SQL Server connection.

You must select this option for Pushdown to function.

| | No | Archive Break Records | Option |

Allows you to write break records directly to a SQL Server database or schema.

Only rule break records are eligible for source archival.

| | Yes | Archive Break Records Location | String |

The break records archive location within SQL Server. If you do not specify a location, then Collibra DQ uses SQLS by default.

Archive Break Records Location is only available and required when the Archive Break Records option is selected.

| | Yes | Driver Location | File path | A file path that designates the name and location of the driver. For example, /opt/owl/drivers/mssql/ | | No | Driver Properties | String | Optional. The configurable driver properties of your connection. | | {% endstep %} | | | | {% step %} Click **Save**. {% endstep %} {% endstepper %} ## What's next You can now [create a Pushdown job](/data-quality-self-hosted/core-concepts/explorer/create-a-dq-job.md) on your SQL Server connection. ## Known limitations * As of the Collibra DQ 2024.02 release, only AdaptiveRules are available from the Add Layers step. * Only native Freeform SQL (PQ) is supported for SQLF rules, meaning that queries in the format of `@dataset` (TLQ) or `@job-name` (LQ) are not supported. Only queries that use native (PQ) are supported. * The use of the 'TOP(limit)' clause for the source is not supported when Link ID is enabled for SQLF rules. This is because the 'TOP N' specification should be placed at the beginning of the query. When Link ID is enabled for rules, it is added to the beginning of the query, causing the Insert query to fail. {% endtab %} {% tab title="SAP Hana" %} This section shows you how to set up [Pushdown](/data-quality-self-hosted/core-concepts/explorer/processing-methods/pushdown-processing.md) for a [SAP HANA connection](/data-quality-self-hosted/connections/supported-connections/supported-jdbc-data-sources/connecting-to-sql-server.md). ## Requirements ### In Collibra DQ * You have admin permissions (`ROLE_ADMIN`) to set up the SAP HANA connection template and enable Pushdown. * You have the SAP HANA JDBC driver for [Standalone](/data-quality-self-hosted/installation/installing-data-quality-observability-self-hosted-on-self-hosted-spark-standalone.md) deployments of Collibra DQ.

You do not need to install the SAP HANA JDBC driver for Installing Data Quality & Observability (self-hosted) on self-hosted Kubernetes deployments of Collibra DQ because it is already included in the installation package.

### In SAP HANA * You have Read access on the SAP HANA database tables on which you run data quality. ## Configuring Pushdown for SAP HANA The following steps show you how to set up the SAP HANA connection template with Pushdown enabled. {% stepper %} {% step %} On the main menu, click , and then click **Connections**. {% endstep %} {% step %} Click **Add Connection**, then click SAP HANA. {% endstep %} {% step %} Enter the required information. | Required | Property | Type | Description | | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------ | --------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | Yes | Name | String | The unique name of your SAP HANA connection. | | Yes | Connection URL | String | The base connection string, for example, `jdbc:sap://${host}:${port}/` | | Yes | Port | Integer | The port number to establish a connection to the datasource. The default port is 39015. | | Yes | Driver Name | String | The driver class name used for your connection, for example, `com.sap.db.jdbc.Driver` | | No | Source Name | String | N/A | | No | Target Agent | Option |

The Agent used to submit your DQ Job.

You do not need to select an option because Pushdown jobs do not require an Agent to submit them to the data warehouse.

| | Yes | Auth Type | Option | The method to authenticate your connection. For more information on authentication methods for SAP HANA connections, go to the [official SAP HANAdocumentation](/data-quality-self-hosted/connections/supported-connections/supported-jdbc-data-sources/connecting-to-sap-hana.md). | | Yes | Pushdown | Checkbox |

Switches Pushdown processing on or off.

Select the checkbox option to turn on Pushdown for your SAP HANA connection.

You must select this option for Pushdown to function.

| | No | Archive Break Records | Option | Allows you to write break records directly to a SAP HANA database or schema. | | Yes | Archive Break Records Location | String |

The break records archive location within SAP HANA. If you do not specify a location, then Collibra DQ uses SAPHANADB by default.

Your default output schema may be one of the following:

  • SAP\
  • SAPSR3
  • SAPBAP<#>
  • SAPHANADB

Archive Break Records Location is only available and required when the Archive Break Records option is selected.

| | Yes | Driver Location | File path | A file path that designates the name and location of the driver. For example, /opt/owl/drivers/sap/ | | No | Driver Properties | String | Optional. The configurable driver properties of your connection. | | {% endstep %} | | | | {% step %} Click **Save**. {% endstep %} {% endstepper %} The following table contains an overview of the data quality features currently available for Pushdown for SAP HANA. ## What's next You can now [create a Pushdown job](/data-quality-self-hosted/core-concepts/explorer/create-a-dq-job.md) on your SAP HANA connection. {% endtab %} {% tab title="Oracle" %} This section shows you how to set up [Pushdown](/data-quality-self-hosted/core-concepts/explorer/processing-methods/pushdown-processing.md) for an [Oracle connection](/data-quality-self-hosted/connections/supported-connections/supported-jdbc-data-sources/connecting-to-oracle.md). ## Prerequisites * You have admin permissions (`ROLE_ADMIN`) to set up the Oracle connection template and enable Pushdown. * You have read access on Oracle database tables. * The Kerberos user has read permissions on Oracle tables (if using Kerberos authentication). ## Configuring Pushdown for Oracle The following steps show you how to set up the Oracle connection template with Pushdown enabled. ### Setting up the Oracle connection template The following steps show you how to set up the Oracle connection template with Pushdown enabled. {% stepper %} {% step %} On the main menu, click , and then click **Connections**. {% endstep %} {% step %} Click the Oracle tile, then enter the required information. | Required | Property | Type | Description | | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------ | --------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | | Yes | Name | String | The unique name of your Oracle connection. | | Yes | Connection URL | String |

The connection string path of your Oracle connection.

When referring to the example below, replace the ${value} sections of the connection URL with your actual value.

:glasses-round: Example: Using SIDjdbc:oracle:thin:@${host}:SID

:glasses-round: Example: Using database service namejdbc:oracle:thin:@//${host}:${port}/service\_name

| | Yes | Port | Integer |

The port number to establish a connection to the datasource.

The default port is 1521

| | Yes | Driver Name | String |

The driver class name of your connection.

oracle.jdbc.OracleDriver

| | No | Source Name | String | N/A | | No | Target Agent | Option |

The Agent used to submit your DQ Job.

You do not need to select an option because Pushdown jobs do not require an Agent to submit them to the data warehouse.

| | Yes | Auth Type | Option | The method to authenticate your connection. For more information on authentication methods for Oracle connections, go to the [official Oracle documentation](/data-quality-self-hosted/connections/supported-connections/supported-jdbc-data-sources/connecting-to-oracle.md). | | Yes | Pushdown | Checkbox |

Switches Pushdown processing on or off.

Select the checkbox option to turn on Pushdown for your Oracle connection.

You must select this option for Pushdown to function.

| | No | Archive Break Records | Option | Allows you to write break records directly to a Oracle database or schema. | | Yes | Archive Break Records Location | String |

The break records archive location within Oracle. If you do not specify a location, then Collibra DQ uses PUBLIC by default.

Archive Break Records Location is only available and required when the Archive Break Records option is selected.

| | Yes | Driver Location | File path | A file path that designates the name and location of the driver. For example, /opt/owl/drivers/oracle | | No | Driver Properties | String | Optional. The configurable driver properties of your connection. | | {% endstep %} | | | | {% step %} Click **Save**. {% endstep %} {% endstepper %} ## What's next You can now [create a Pushdown job](/data-quality-self-hosted/core-concepts/explorer/create-a-dq-job.md) on your Oracle connection. {% endtab %} {% endtabs %}