# Databricks

{% hint style="warning" %}
**IP RESTRICTIONS**

Make sure to allow traffic from one of the Paradime IPs in your firewall depending on the data location selected.

👉 See also: [Paradime IP addresses](/app-help/developers/ip-restrictions.md).
{% endhint %}

## Add Scheduler Connection

To add the Databricks Scheduler connection, complete the following steps:

1. Click **Settings** in the top menu bar of the Paradime interface to access **Account Settings**
2. In the left sidebar, click "**Connections**"
3. Click "**Add New**" next to the **Bolt Schedules** section
4. Select "databricks" and fill out the cooresponding fields.

<figure><img src="/files/GoyQcGDps8lrQXu3Uwg0" alt="" width="540"><figcaption></figcaption></figure>

### Fields details

Below are list of fields and example to create a connection.

| Field                         | Description                                                                                                                                     | Example                                      |
| ----------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------- |
| Profile Name                  | The profile name set in your `dbt_project.yaml` . See more [here](https://docs.getdbt.com/docs/core/connect-data-platform/connection-profiles). | **`dbt-databricks`**                         |
| Target                        | The target name used to identify the connection. See more [here](https://docs.getdbt.com/reference/dbt-jinja-functions/target).                 | **`prod`**                                   |
| Service Host Name             | Databricks server hostname                                                                                                                      | **`dbc-e7c65a5c-0521.cloud.databricks.com`** |
| HTTP path                     | Databricks compute resources URL                                                                                                                | **`/sql/1.0/warehouses/fbc246efa4369412`**   |
| Unity Catalog Name (Optional) | The name of the Unity Catalog. See more [here](https://docs.databricks.com/data-governance/unity-catalog/index.html).                           | **`analytics`**                              |
| Service Principal Token (SPT) | The SPT created for your service user. See more [here](https://docs.databricks.com/dev-tools/service-principals.html#use-curl-or-postman).      | **`dapid7cc51fb15d5889136351110e66119b3`**   |
| Schema                        | The default schema used to build dbt™️ objects at runtime.                                                                                      | **`dbt_prod`**                               |
| Threads                       | The number of threads used in this connection. See more [here](https://docs.getdbt.com/docs/running-a-dbt-project/using-threads).               | **`8`**                                      |


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.paradime.io/app-help/documentation/settings/connections/scheduler-environment/databricks.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.