---
schema_version: "1"
id: 0433da9c115674ee7b656893108dba4a514d2b817686c207f87e288ade57c573
title: Databricks Connection
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/analytics/264-0-0/bi_integrate_connectors_databricks.md
canonical_url: https://help.salesforce.com/s/articleView?id=analytics.bi_integrate_connectors_databricks.htm&release=264.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: 466380435ea4b7920a90e3b559e6b243c6eb27209fa763de28931af29a812e03
description: Sync Databricks to CRM Analytics by creating a remote connection..
products:
  - CRM Analytics
  - Cross Cloud
release: "264"
---
# Databricks Connection

Sync Databricks to CRM Analytics by creating a remote connection..

## Create the Connection

1. On the Data Manager Connections tab, click **New Connection**.
2. Click the name of the connector, and click **Next**.
3. Enter the connector settings.
4. To validate your settings and attempt to connect to the source, click **Save & Test**. If the connection fails, CRM Analytics shows possible reasons.

## Connect to Databricks with OAuth

To use the Databricks connector with OAuth authentication, you must configure your Databricks service principal and generate a client ID and secret. See Databricks help [Authorize unattended access to Databricks resources with a service principal using OAuth](https://docs.databricks.com/aws/en/dev-tools/auth/oauth-m2m) for more information.

Databricks uses machine-to-machine (M2M) OAuth authentication, which provides additional security, and allows you to specify, at finer granularities, which objects can be accessed and the specific access privileges granted for these objects. With M2M OAuth, no external authentication provider is required.

You specify the client ID and a client secret to use for authentication in the connection settings. Databricks sets an expiration data on these values, which needs to be managed. When you generate the OAuth secret in Databricks, you can set the secret lifetime in days, with a maximum of 730 days (2 years). When client ID and secret values expire, you must update your Databricks connection with the updated values.

## Connection Settings

All settings are required.

 
| Setting | Description |
| --- | --- |
| Connection Name | Required. The connection name. Use a name that lets you easily distinguish between different connections. |
| Developer Name | Required. The API name is used in your recipes to reference data extracted through this connection. The name can't include spaces. After you create the connection, you can't change the developer name. |
| Description | Required. The connection description. |
| Authentication Type | Required. The authentication type. Valid values are `OAuth` and `Token`. |
| Token | Required for token authentication. The personal access token for Databricks. You can find the value on your Databricks User Settings page on the Access Tokens tab. |
| Client Id | Required for OAuth authentication. The Databricks generated client ID. You can find the value on your Databricks Service Prinipal page on the Secrets tab. This value expires and must be updated when a new secret is generated. |
| Client Secret | Required for OAuth authentication. The Databricks generated client secret. You can find the value on your Databricks Service Prinipal page on the Secrets tab. This value expires and must be updated when a new secret is generated. |
| Server | Required. The server hostname of the Databricks cluster. |
| HTTPPath | Required. The HTTP path of the Databricks cluster. |
| Database | Required. The name of the Databricks database. |
| Schema | Required. The name of the Databricks database. |
| Catalog | Required. The name of the Databricks catalog. Defaults to hive\_metastore. |

![Note](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-analytics-bi-264-0-0-production-enus/ec791473-f5b4-4f64-a656-9104f455d966/images/icon_note.png)

Note In Databricks, database and schema are synonymous. Enter the same value for both settings.

For more information, see [Establishing a Connection](https://cdn.cdata.com/help/LKJ/jdbc/pg_connectionj.htm).

## Connection Considerations

When working with the Databricks connector, keep these behaviors in mind.

- Connected object names must start with a letter and contain only letters, digits, or underscores. Object names can't end with an underscore.
- Only field names with combinations of alphanumeric, dot, underscore, or dash characters are supported. If a connector includes field names that contain other characters, such as spaces or brackets, the sync fails.
- This connector can sync up to 10 million rows or up to 5 GB per job, whichever limit it reaches first.