![]() |
VOOZH | about |
CData Sync is a standalone application that supports a wide range of replication scenarios, including replicating both sandbox and production instances into your database. By replicating Databricks data to a PostgreSQL database in Heroku, you can access Databricks external objects (via Salesforce Connect) alongside standard Salesforce objects.
Accessing and integrating live data from Databricks has never been easier with CData. Customers rely on CData connectivity to:
While many customers are using CData's solutions to migrate data from different systems into their Databricks data lakehouse, several customers use our live connectivity solutions to federate connectivity between their databases and Databricks. These customers are using SQL Server Linked Servers or Polybase to get live access to Databricks from within their existing RDBMs.
Read more about common Databricks use-cases and how CData's solutions help solve data problems in our blog: What is Databricks Used For? 6 Use Cases.
For this replication example, you need the following:
Using CData Sync, you can easily replicate data from Databricks data to a PostgreSQL database on Heroku. For this article, you will need an existing PostgreSQL database on Heroku. To add your PostgreSQL database as a replication destination, navigate to the Connections tab.
You are now connected to PostgreSQL and can use it as both a source and a destination.
NOTE: You can use the Label feature to add a label for a source or a destination.
π Add a label.You can configure a connection to Databricks from the Connections tab. To add a connection to your Databricks account, navigate to the Connections tab.
To connect to a Databricks cluster, set the properties as described below.
Note: The needed values can be found in your Databricks instance by navigating to Clusters, and selecting the desired cluster, and selecting the JDBC/ODBC tab under Advanced Options.
CData Sync enables you to control replication with a point-and-click interface and with SQL queries. For each replication you wish to configure, navigate to the Jobs tab and click Add Job. Select the Source and Destination for your replication.
π Select Source and Destination connections for the replication.To replicate an entire table, navigate to the Task tab in the Job, click Add Tasks, choose the table(s) from the list of Databricks tables you wish to replicate into PostgreSQL, and click Add Tasks again.
π Choose entire tables to replicate (Salesforce is shown).You can use the Columns and Query tabs of a task to customize your replication. The Columns tab allows you to specify which columns to replicate, rename the columns at the destination, and even perform operations on the source data before replicating. The Query tab allows you to add filters, grouping, and sorting to the replication with the help of SQL queries.
π Configure a replication.As you make changes using the interface, the SQL query used for the replication changes, going from something simple, like this:
REPLICATE [Customers]
to something customized and more complex, like this:
REPLICATE [Customers] SELECT [City], [CompanyName] FROM [Customers] WHERE [Country] = US
Select the Overview tab in the Job, and click Configure under Schedule. You can schedule a job to run automatically by configuring it to run at specified intervals, ranging from once every 10 minutes to once every month.
π Schedule your job to run automatically.Once you have configured the replication job, click Save Changes. You can configure any number of jobs to manage the replication of your Databricks data to PostgreSQL.
Once all the required configurations are made for the job, select the Databricks table you wish to replicate and click Run. After the replication completes successfully, a notification appears, showing the time taken to run the job and the number of rows replicated.
π Run the job.The Databricks data tables are now replicated in Heroku PostgreSQL database.
Once your Databricks data is replicated to the PostgreSQL database on Heroku, configure the OData interface for Heroku and connect to the database as an external data source via Salesforce Connect.
The first part of connecting to Databricks data replicated to a PostgreSQL database on Heroku is configuring the Heroku External Objects for the database.
Refer to the Heroku documentation for more detailed instructions.
After the OData service for Heroku is configured, we can connect to the replicated Databricks data as an external data source from Salesforce Connect.
After you have created the external data source in Salesforce, follow the steps below to create Databricks external objects that reflect any changes in the data source. You will synchronize the definitions for the Databricks external objects with the definitions for Databricks tables.
At this point, you will be able to connect to and work with your replicated Databricks entities as external objects just as you would with standard Salesforce objects, whether you are simply viewing the data or building related lists of external Databricks data alongside standard Salesforce objects.
Download a 30-day free trial of CData Sync and replicate your Databricks data for use with Salesforce Connect today!
Learn more or sign up for a free trial:
CData Sync