> 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/connections/connect-to-a-jdbc-or-remote-file-data-source.md).
# Connect to a JDBC or remote file data source
This topic shows you how to create a new data source connection.
{% hint style="success" %}
For more information on the data sources supported by Data Quality & Observability (self-hosted), see [Supported Connections](/data-quality-self-hosted/connections/supported-connections.md).
{% endhint %}
## Prerequisites
To add a connection, you need:
* A Collibra DQ account with ROLE\_ADMIN or ROLE\_CONNECTION\_MANAGER permissions.
* Access to the account credentials of your connection, for example, PostgreSQL.
## Adding a JDBC or remote file connection
This section shows you how to connect to a JDBC or remote file data source from the Connection Management page. Select an option from the tabs below.
{% tabs %}
{% tab title="JDBC Connections" %}
{% stepper %}
{% step %}
Sign in to Collibra DQ.
{% endstep %}
{% step %}
Hover your cursor over the 
icon and click **Admin Console**.\ :chevrons-right: The Admin Console opens.
{% endstep %}
{% step %}
Click **Connections**.\ :chevrons-right: The **Connection Management** page opens.
{% endstep %}
{% step %}
Click **Add Connection** in the upper-right corner.\ :chevrons-right: The **Add New Connection** dialog box opens to the JDBC Connections tab with a list of [supported JDBC data sources](/data-quality-self-hosted/connections/supported-connections/supported-jdbc-data-sources.md).
{% endstep %}
{% step %}
Click a data source.\ :chevrons-right: The **Add Connection** template appears.
{% endstep %}
{% step %}
Enter the required information.
***
**Details**
| Required | Option | Type | Value |
|---|
| Connection Details |
 Yes | Name | String | The unique name used for your connection. Do not use single quotes (') or double quotes (") in the connection name. When a job runs, the connection name is passed as a command-line argument. Quote characters cause the argument to be parsed incorrectly, which makes the connection name malformed and causes the job to fail. |
| Yes | Connection URL | String | The connection string value of your connection. The Connection URL uses the following format: jdbc:<datasource>://$host:<port>/<AdditionalProperties>
Replace the Connection URL to point to the database server to run DQ Jobs against. |
| Yes | Port | Integer | The port for the connection to the data source host. |
 No | Limit Schemas | Option | Allows you to manage usage and restrict visibility to only the necessary schemas in the Explorer tree. See Limiting schemas to learn how to limit schemas from the Connection Management page. When you include a restricted schema in the query of a DQ Job, the query scope may be overwritten when the job runs. While only the schemas you selected when you set up the connection are shown in the Explorer menu, users are not restricted from running SQL queries on any schema from the data source. |
| Connection Credentials |
| Yes | Authentication Type | Option | The method to authenticate your connection. The configuration requirements differ depending on the authentication type you select. Additional options on the connection template, such as Username and Password, will appear depending on the authentication type you select. |
| No | Pushdown | Option | Enables Pushdown processing. This option is required for Pushdown Job submission. |
| No | Source Name | String | The alias name of your connection. While this is optional, you can use this to make it easier to identify your connection in API payloads. There are no character restrictions for the Source Name field, but it is best practice to use only alphanumeric characters, hyphens, and underscores. |
| No | Target Agents | String | The Agent used to submit your DQ Job. |
***
**Properties**
| Required | Property | Type | Value |
|---|
| Yes | Driver Location | File path | The location where your driver file is saved. Click Upload to specify the Directory Name and select a Driver File. |
| Yes | Driver Name | String | The driver class name. For example, a BigQuery JDBC driver may use the following convention: com.simba.googlebigquery.jdbc42.Driver
|
| No | Driver Properties | String | The configurable driver properties of your connection. The supported format is [{"name":"prop1","value":"val1"},{"name":"prop2","value":"val2"}] |
***
**Variables**
| Required | Property | Type | Value |
| ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------- | ------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Yes
(when using)
| Variable Name | String | The variable to display in place of sensitive information, such as Password, or a variable that must be URL-encoded because it uses special characters (spaces, ampersands, equals signs, etc.), such as a Snowflake query\_tag.
In the Connection URL, replace the sensitive information with this value. In the following example, dquser and dqpassword are the property names that replace the sensitive variable values: jdbc:postgresql://localhost:5432/postgres?user=${dquser}\&password=${dqpassword}
|
| Yes
(when using)
| Value | String | The sensitive value to hide in the Connection URL. For example, if the password value of the connection credential is "password123", enter password123 in the property value field.
Commas and equals signs are supported characters. For example, val1=,val2 is a valid format.
The connection string value of your connection.
:glasses-round: Example: s3://dq-datasets-123
|
| Yes | Authentication Type | Option | The method to authenticate your connection.
The configuration requirements differ depending on the authentication type you select. Additional options on the connection template, such as Keytab, will appear depending on the authentication type you select.
The path along which break records will be archived when the Archive Break Records and HTTPS options are enabled.
Specify a schema output location in your data source for break records to send. For example, /write/FolderName
This option is only available when the HTTPS option is enabled.
The configurable driver properties of your connection.
The supported format is \[{"name":"prop1","value":"val1"},{"name":"prop2","value":"val2"}]
|
***
**Variables**
| Required | Property | Type | Value |
| ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------- | ------ | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Yes
(when using)
| Variable Name | String | The variable to display in place of the sensitive information. This can be any variable, such as Password
In the Connection URL, replace the sensitive information with this value. In the following example, dquser and dqpassword are the property names that replace the sensitive variable values: jdbc:postgresql://localhost:5432/postgres?user=${dquser}\&password=${dqpassword}
|
| Yes
(when using)
| Value | String | The sensitive value to hide in the Connection URL. For example, if the password value of the connection credential is "password123", enter password123 in the property value field.
Commas and equals signs are supported characters. For example, val1=,val2 is a valid format.