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.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.
View the full entity schema
See every table and column exported to your destination, organized by entity group.
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
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).1
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).
2
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 CATALOGon 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
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.3
Connect Stigg with Databricks
In Stigg, navigate to Integrations > Apps > Databricks.Enter the following information in the connection form:
Click Test & connect.
4
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 for a description of each group.