> For the complete documentation index, see [llms.txt](https://docs.codatum.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.codatum.com/connect-and-manage-data/supported-warehouses/databricks.md).

# Databricks

With Codatum, you can connect, query, and manage data of Databricks.

{% hint style="warning" %}
This feature is currently in preview. Functionality and availability may change without notice.

We'd love your feedback.
{% endhint %}

## How to Set Up

Databricks integration targets Serverless SQL Warehouses.

### 1. Necessary preparations in Databricks Console

Creat a service principal for integration and assign the appropriate permissions.

#### Account Admin Page

* From the menu, go to User Management > Service Principals and create a service principal for integration
* In the service principal's Credentials and Secrets tab, generate an OAuth secret. Save the client ID and secret at this time
* In the service principal's Roles tab, turn OFF all settings
* From the menu, select Workspaces, choose the workspace to integrate, go to the Permissions tab, and add the created service account

#### Workspace Admin Page

* Grant the service principal "Can Use" permission for the SQL Warehouse to connect
  * From the menu, go to SQL Warehouses and select the warehouse to integrate
  * Click the Permissions button in the upper right and grant the service principal `Can Use` permission
* Grant the service principal permissions to use the catalog
  * From the menu, go to Catalogs and select the catalog to integrate
  * In the Permissions tab, click the Grant button, select the service principal, and grant `SELECT`, `USE CATALOG`, and `USE SCHEMA` permissions

### 2. Register Databricks connection in Codatum

* From `Workspace Settings`, go to `Connections` and select `New Connection`
* Enter the `Connection Name`
* Enter the `Access Level`
* Enter the `Server Host Name`
  * In Databricks Workspace Console, go to SQL Warehouses from the menu, select the warehouse to integrate, and find the Server Hostname in the Connection Details tab (e.g., `<your_instance_name>.cloud.databricks.com`)
* Enter the `HTTP Path`
  * In Databricks Workspace Console, go to SQL Warehouses from the menu, select the warehouse to integrate, and find the HTTP Path in the Connection Details tab (e.g., `/sql/1.0/warehouses/<your_warehouse_id>`)
* Enter the `Warehouse ID`
  * In Databricks Workspace Console, go to SQL Warehouses from the menu, select the warehouse to integrate, and find the ID next to the Name in the Overview tab
* Enter the `Client ID`
  * The client ID of the service principal created in step 1
* Enter the `Client Secret`
  * The client secret of the service principal created in step 1

Once you've entered all the information, run a connection test and save the connection.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## 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, and the optional `goal` query parameter:

```
GET https://docs.codatum.com/connect-and-manage-data/supported-warehouses/databricks.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.