> ## Documentation Index
> Fetch the complete documentation index at: https://docs.paradime.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Databricks

> Connect Databricks to Paradime to run dbt™ against your SQL warehouse or all-purpose cluster from the Code IDE, Bolt, and Agent environments.

[Databricks](https://www.databricks.com/) is a cloud data platform for storing, processing, and analyzing your data. Connect it to Paradime to run dbt™ from the Code IDE, deploy production jobs with Bolt, and let the DinoAI background agent work against your warehouse.

<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](/developers/ip-restrictions).
</Warning>

<Note>
  **Available in:** Code IDE, Bolt, and Agent environments.
</Note>

## Add a connection

1. Click **Settings** in the top menu bar of the Paradime interface to access **Workspace Settings**.
2. In the left sidebar, click **Environments**.
3. Click **Add New** next to the section for the environment you are configuring:
   * **Code IDE** for the Code IDE connection
   * **Bolt** for the Bolt connection
   * **Agent** for the Agent connection
4. Select **Databricks** and fill out the corresponding fields.

## Field details

Set **Target** to match the environment you are configuring (`dev`, `prod`, or `dinoai`). The Code IDE environment uses a Personal Access Token (PAT), while the Bolt and Agent environments use a Service Principal Token (SPT).

<Info>
  Field access levels apply only to the **Code IDE** environment: an `Admin` sets workspace-level fields, and each developer sets their own user-level fields. In the Bolt and Agent environments, an `Admin` sets all fields.
</Info>

| 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).                                                 | **`dev`**                                    |
| 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`**                              |
| Personal Access Token (PAT)   | The PAT created by each user, for the Code IDE environment. See more [here](https://docs.databricks.com/dev-tools/auth.html).                                                   | **`dapid7cc51fb15d5889136351110e66119b3`**   |
| Service Principal Token (SPT) | The SPT created for your service user, for the Bolt and Agent environments. 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_john`**                               |
| Threads                       | The number of threads used in this connection. See more [here](https://docs.getdbt.com/docs/running-a-dbt-project/using-threads).                                               | **`8`**                                      |

## Related

<CardGroup cols={2}>
  <Card title="Optional connection attributes" href="/guides/data-warehouse-essentials/optional-connection-attributes" icon="gear" horizontal>
    Set additional `profiles.yml` attributes for this connection.
  </Card>
</CardGroup>


## Related topics

- [Databricks Tools](/products/dino-ai/tools-and-features/warehouse-tool/databricks-tools.md)
- [Tools Reference](/products/dino-ai/programmable-agents/tools-reference.md)
- [DinoAI Tools](/products/dino-ai/tools-and-features/index.md)
- [Creating a Workspace](/guides/paradime-101/getting-started-with-your-paradime-workspace/creating-a-workspace.md)
- [Radar environment](/products/settings/connections/cost-connection/index.md)