Migrating data from Phoenix to Databricks using CData SSIS Components.

Databricks is a unified data analytics platform that allows organizations to easily process, analyze, and visualize large amounts of data. It combines data engineering, data science, and machine learning capabilities in a single platform, making it easier for teams to collaborate and derive insights from their data.

The CData SSIS Components enhance SQL Server Integration Services by enabling users to easily import and export data from various sources and destinations.

In this article, we explore the data type mapping considerations when exporting to Databricks and walk through how to migrate Phoenix data to Databricks using the CData SSIS Components for Phoenix and Databricks.

Data Type Mapping

Special Considerations

• String/VARCHAR: String columns from Databricks can map to different data types depending on the length of the column. If the column length exceeds 4000, then the column is mapped to nvarchar (max). Otherwise, the column is mapped to nvarchar (length).
• DECIMAL Databricks supports DECIMAL types up to 38 digits of precision, but any source column beyond that can cause load errors.

Prerequisites

• Visual Studio 2022
• SQL Server Integration Services Projects extension for Visual Studio 2022
• CData SSIS Components for Databricks
• CData SSIS Components for Phoenix

Create the project and add components

1. Open Visual Studio and create a new Integration Services Project. 👁 Create the SSIS project
   
2. Add a new Data Flow Task to the Control Flow screen and open the Data Flow Task.
3. Add a CData Phoenix Source control and a CData Databricks Destination control to the data flow task. 👁 Add the source and destination controls (Salesforce is shown)
   

Configure the Phoenix source

Follow the steps below to specify properties required to connect to Phoenix.

1. Double-click the CData Phoenix Source to open the source component editor and add a new connection. 👁 Open the source component editor (Salesforce is shown)
   
2. In the CData Phoenix Connection Manager, configure the connection properties, then test and save the connection.

   Connect to Apache Phoenix via the Phoenix Query Server. Set the Server and Port (if different from the default port) properties to connect to Apache Phoenix. The Server property will typically be the host name or IP address of the server hosting Apache Phoenix.

   Authenticating to Apache Phoenix

   By default, no authentication will be used (plain). If authentication is configured for your server, set AuthScheme to NEGOTIATE and set the User and Password properties (if necessary) to authenticate through Kerberos. 👁 Configure the source connection (Salesforce is shown)
   

3. After saving the connection, select "Table or view" and select the table or view to export into Databricks, then close the CData Phoenix Source Editor. 👁 Select the table to export (Salesforce is shown)
   

Configure the Databricks destination

With the Phoenix Source configured, we can configure the Databricks connection and map the columns.

1. Double-click the CData Databricks Destination to open the destination component editor and add a new connection. 👁 Open the destination component editor
   
2. In the CData Databricks Connection Manager, configure the connection properties, then test and save the connection. 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, selecting the desired cluster, and selecting the JDBC/ODBC tab under Advanced Options.

   • Server: Set to the Server Hostname of your Databricks cluster.
   • HTTPPath: Set to the HTTP Path of your Databricks cluster.
   • Token: Set to your personal access token (this value can be obtained by navigating to the User Settings page of your Databricks instance and selecting the Access Tokens tab).

   Other helpful connection properties

   • QueryPassthrough: When this is set to True, queries are passed through directly to Databricks.
   • ConvertDateTimetoGMT: When this is set to True, the components will convert date-time values to GMT, instead of the local time of the machine.
   • UseUploadApi: Setting this property to true will improve performance if there is a large amount of data in a Bulk INSERT operation.
   • UseCloudFetch: This option specifies whether to use CloudFetch to improve query efficiency when the table contains over one million entries.
   👁 Configure the destination connection
   
3. After saving the connection, select a table in the Use a Table menu and in the Action menu, select Insert. 👁 Choose the destination table
   
4. On the Column Mappings tab, configure the mappings from the input columns to the destination columns. 👁 Map the columns (Salesforce is shown)
   

Run the project

You can now run the project. After the SSIS Task has finished executing, data from your SQL table will be exported to the chosen table.