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

# Databricks

## Overview

Stigg's integration with Databricks allows you to export your product catalog, customer, and subscription data directly to a Databricks SQL warehouse for analytics and data engineering workflows.

<Note>
  Stigg's native data export integrations are included in the Scale plan, and are also available as an optional add-on to the Growth plan. See Stigg's pricing for more details.
</Note>

<Card title="View the full entity schema" icon="sitemap" href="./schema">
  See every table and column exported to your destination, organized by entity group.
</Card>

## Setting up the integration

### Prerequisites

* A Databricks workspace with a SQL warehouse. Unity Catalog is used by default; Hive Metastore is also supported.
* A service principal (recommended) or personal access token with permission to use the warehouse and read/write the target catalog and schema

<Note>
  If your workspace restricts access with IP Access Lists, allowlist Stigg's static egress IP: `35.192.85.117/32` (US) or `104.199.49.149/32` (EU).
</Note>

<Steps>
  <Step title="Create a SQL warehouse">
    In your Databricks workspace, go to **SQL Warehouses > Create SQL Warehouse**, name it, and configure its size. In **Advanced options**, make sure **Unity Catalog** is toggled on (unless you're using Hive Metastore).
  </Step>

  <Step title="Create a service principal (recommended)">
    Go to **Settings > Identity and access > Service Principals > Manage** and create a new service principal. Generate an OAuth secret (choose a lifetime of 90, 180, or 365 days) and record the **Client ID** and **Secret**.

    Grant the service principal:

    * **Can use** on the SQL warehouse created above
    * `USE CATALOG` on the target catalog
    * On the target schema, either `ALL PRIVILEGES`, or all of: `USE SCHEMA`, `APPLY TAG`, `MODIFY`, `READ VOLUME`, `SELECT`, `WRITE VOLUME`, `CREATE MATERIALIZED VIEW`, `CREATE TABLE`, `CREATE VOLUME`

    <Warning>
      A missing `USE CATALOG` grant is the most common cause of test-connection failures.
    </Warning>

    <Note>
      Using a personal access token instead? From the SQL warehouse's **Connection Details** tab, record the **Server hostname**, **Port**, and **HTTP path**, then generate a token (select the `sql` scope if PAT scopes are enabled). Grant it the same `USE CATALOG` and schema-level privileges as above. OAuth with a service principal is recommended over a personal access token for better security and token lifecycle management.
    </Note>
  </Step>

  <Step title="Connect Stigg with Databricks">
    In [Stigg](https://app.stigg.io/), navigate to **Integrations > Apps > Databricks**.

    Enter the following information in the connection form:

    | Field             | Description                                                                   |
    | ----------------- | ----------------------------------------------------------------------------- |
    | Server hostname   | The SQL warehouse hostname, from the **Connection Details** tab               |
    | Port              | The SQL warehouse port, from the **Connection Details** tab. Typically `443`. |
    | HTTP path         | The HTTP path, from the **Connection Details** tab                            |
    | Catalog           | The target Unity Catalog name (or `hive` if using Hive Metastore)             |
    | Schema            | The schema where Stigg will create and sync tables                            |
    | Auth method       | **OAuth (service principal)** (recommended) or **Personal access token**      |
    | Client ID / Token | The OAuth client ID, or the personal access token                             |
    | Client secret     | The OAuth client secret (OAuth only)                                          |

    Click **Test & connect**.
  </Step>

  <Step title="Select entities to export">
    After entering your connection details, expand the **Entities to export** section to choose which entity groups to include in the sync. All groups are selected by default.

    See [Exported entities](./overview#exported-entities) for a description of each group.
  </Step>
</Steps>


## Related topics

- [Exported entities](/documentation/importing-and-exporting-data/export/overview.md#exported-entities)
- [Sync process, schedule, manual sync, and sync history](/documentation/importing-and-exporting-data/export/overview.md#sync-process)