Databricks is a leading AI cloud-native platform that unifies data engineering, machine learning, and analytics at scale.
Its powerful data lakehouse architecture combines the performance of data warehouses with the flexibility of data lakes.
Integrating Databricks with CData Connect AI
gives organizations live, real-time access to AlloyDB data without the need for complex ETL pipelines or
data duplication—streamlining operations and reducing time-to-insights.
In this article, we'll walk through how to configure a secure, live connection from Databricks to AlloyDB
using CData Connect AI. Once configured, you'll be able to access AlloyDB data directly from Databricks notebooks
using standard SQL—enabling unified, real-time analytics across your data ecosystem.
Overview
Here is an overview of the simple steps:
-
Step 1 — Connect and Configure:
In CData Connect AI, create a connection to your AlloyDB source, configure user permissions,
and generate a Personal Access Token (PAT).
-
Step 2 — Query from Databricks:
Install the CData JDBC driver in Databricks, configure your notebook with the connection details,
and run SQL queries to access live AlloyDB data.
Prerequisites
Before you begin, make sure you have the following:
-
An active AlloyDB account.
-
A CData Connect AI account. You can log in or
sign up for a free trial here.
-
A Databricks account. Sign up or log in here.
Step 1: Connect and Configure a AlloyDB Connection in CData Connect AI
1.1 Add a Connection to AlloyDB
CData Connect AI uses a straightforward, point-and-click interface to connect to available data sources.
-
Log into Connect AI, click Sources on the left, and then
click Add Connection in the top-right.
👁 Adding a Connection in CData Connect AI
- Select "AlloyDB" from the Add Connection panel.
👁 Selecting a data source
-
Enter the necessary authentication properties to connect to AlloyDB.
The following connection properties are usually required in order to connect to AlloyDB.
- Server: The host name or IP of the server hosting the AlloyDB database.
- User: The user which will be used to authenticate with the AlloyDB server.
- Password: The password which will be used to authenticate with the AlloyDB server.
You can also optionally set the following:
- Database: The database to connect to when connecting to the AlloyDB Server. If this is not set, the user's default database will be used.
- Port: The port of the server hosting the AlloyDB database. This property is set to 5432 by default.
Authenticating with Standard Authentication
Standard authentication (using the user/password combination supplied earlier) is the default form of authentication.
No further action is required to leverage Standard Authentication to connect.
Authenticating with pg_hba.conf Auth Schemes
There are additional methods of authentication available which must be enabled in the pg_hba.conf file on the AlloyDB server.
Find instructions about authentication setup on the AlloyDB Server here.
Authenticating with MD5 Authentication
This authentication method must be enabled by setting the auth-method in the pg_hba.conf file to md5.
Authenticating with SASL Authentication
This authentication method must be enabled by setting the auth-method in the pg_hba.conf file to scram-sha-256.
Authenticating with Kerberos
The authentication with Kerberos is initiated by AlloyDB Server when the ∏ is trying to connect to it. You should set up Kerberos on the AlloyDB Server to activate this authentication method. Once you have Kerberos authentication set up on the AlloyDB Server, see the Kerberos section of the help documentation for details on how to authenticate with Kerberos.
👁 Configuring a connection (Salesforce is shown)
-
Click Save & Test in the top-right.
-
Navigate to the Permissions tab on the AlloyDB Connection page
and update the user-based permissions based on your preferences.
👁 Updating permissions
1.2 Generate a Personal Access Token (PAT)
When connecting to Connect AI through the REST API, the OData API, or the Virtual SQL Server,
a Personal Access Token (PAT) is used to authenticate the connection to Connect AI. PAT functions as an
alternative to your login credentials for secure, token-based authentication. It is a best practice to
create a separate PAT for each service to maintain granularity of access.
-
Click on the Gear icon () at the top right of the Connect AI app to open the settings page.
-
On the Settings page, go to the Access Tokens section and click Create PAT.
-
Give the PAT a name and click Create.
👁 Creating a new PAT
-
Note: The personal access token is only visible at creation, so be sure to copy it and store it securely for future use.
Step 2: Connect and Query AlloyDB Data in Databricks
Follow these steps to establish a connection from Databricks to AlloyDB.
You'll install the CData JDBC Driver for Connect AI, add the JAR file to your cluster, configure your notebooks,
and run SQL queries to access live AlloyDB data data.
2.1 Install the CData JDBC Driver for Connect AI
-
In CData Connect AI, click the Integrations page on the left.
Search for JDBC or Databricks, click Download,
and select the installer for your operating system.
-
Once downloaded, run the installer and follow the instructions:
-
For Windows: Run the setup file and follow the installation wizard.
-
For Mac/Linux: Unpack the archive and move the folder to /opt or
/Applications. Make sure you have execute permissions.
-
After installation, locate the JAR file in the installation directory:
2.2 Install the JAR File on Databricks
-
Log in to Databricks. In the navigation pane, click Compute on the left. Start or create a compute cluster.
👁 Launching a compute cluster in Databricks
-
Click on the running cluster, go to the Libraries tab, and click Install New at the top right.
👁 Accessing the Libraries tab in Databricks
-
In the Install Library dialog, select DBFS, and drag and drop the
cdata.jdbc.connect.jar file. Click Install.
👁 Uploading the JDBC driver JAR to DBFS
2.3 Query AlloyDB Data in a Databricks Notebook
Notebook Script 1 — Define JDBC Connection:
- Paste the following script into the notebook cell:
driver = "cdata.jdbc.connect.ConnectDriver"
url = "jdbc:connect:AuthScheme=Basic;User=your_username;Password=your_pat;URL=https://cloud.cdata.com/api/;DefaultCatalog=Your_Connection_Name;"
- Replace:
- your_username - With your CData Connect AI username
- your_pat - With your CData Connect AI Personal Access Token (PAT)
- Your_Connection_Name - With the name of your Connect AI data source, from the Sources page
- Run the script.
Notebook Script 2 — Load DataFrame from AlloyDB data:
- Add a new cell for this second script. From the menu on the right side of your notebook, click Add cell below.
- Paste the following script into the new cell:
remote_table = spark.read.format("jdbc") \
.option("driver", "cdata.jdbc.connect.ConnectDriver") \
.option("url", "jdbc:connect:AuthScheme=Basic;User=your_username;Password=your_pat;URL=https://cloud.cdata.com/api/;DefaultCatalog=Your_Connection_Name;") \
.option("dbtable", "YOUR_SCHEMA.YOUR_TABLE") \
.load()
- Replace:
- your_username - With your CData Connect AI username
- your_pat - With your CData Connect AI Personal Access Token (PAT)
- Your_Connection_Name - With the name of your Connect AI data source, from the Sources page
- YOUR_SCHEMA.YOUR_TABLE - With your schema and table, for example, AlloyDB.Orders
- Run the script.
Notebook Script 3 — Preview Columns:
- Similarly, add a new cell for this third script.
- Paste the following script into the new cell:
display(remote_table.select("ColumnName1", "ColumnName2"))
- Replace ColumnName1 and ColumnName2 with the actual columns from your AlloyDB structure (e.g. ShipName, ShipCity, etc.).
- Run the script.
👁 Previewing AlloyDB data data in Databricks notebook
You can now explore, join, and analyze live AlloyDB data directly within Databricks
notebooks—without needing to know the complexities of the back-end API and without replicating AlloyDB data.
Try CData Connect AI Free for 14 Days
Ready to simplify real-time access to AlloyDB data?
Start your free 14-day trial of CData Connect AI today
and experience seamless, live connectivity from Databricks to AlloyDB.
Low code, zero infrastructure, zero replication — just seamless, secure access to your
most critical data and insights.