Migrating data from Outlook 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 Outlook data to Databricks using the CData SSIS Components for Outlook 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 Outlook

Create the project and add components

1. Open Visual Studio and create a new Integration Services Project.
2. Add a new Data Flow Task to the Control Flow screen and open the Data Flow Task.
3. Add a CData Outlook Source control and a CData Databricks Destination control to the data flow task.

Configure the Outlook source

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

1. Double-click the CData Outlook Source to open the source component editor and add a new connection.
2. In the CData Outlook Connection Manager, configure the connection properties, then test and save the connection.

   Using OAuth Authentication

   Microsoft Graph API uses OAuth 2.0 for authentication. You must register an application in the Microsoft Azure Portal to obtain OAuth credentials (Client ID and Client Secret).

   Obtaining OAuth Credentials

   1. Log in to the Azure Portal.
   2. Navigate to Azure Active Directory > App registrations.
   3. Click New registration to create a new application.
   4. Enter an application name and select the appropriate account types.
   5. Set the Redirect URI to your application's callback URL (e.g., http://localhost:33333 for desktop apps).
   6. Click Register to create the application.
   7. On the application overview page, copy the Application (client) ID - this is your OAuthClientId.
   8. Navigate to Certificates & secrets and create a new client secret.
   9. Copy the client secret value - this is your OAuthClientSecret.
   10. Navigate to API permissions and add the required Microsoft Graph API permissions:
       • Mail.Read - For accessing email messages
       • Contacts.Read - For accessing contacts
       • Calendars.Read - For accessing calendar events
       • Tasks.Read - For accessing To Do tasks
       • offline_access - For obtaining refresh tokens
   11. Click Grant admin consent to grant these permissions.

   Connecting with OAuth

   After setting the following connection properties, you are ready to connect:

   • AuthScheme: Set this to OAuth.
   • InitiateOAuth: Set this to GETANDREFRESH. The CData API Profile for Outlook will automatically walk through the OAuth process in order to obtain the access token.
   • OAuthClientId: Set this to the Application (client) ID from Azure Portal.
   • OAuthClientSecret: Set this to the client secret value from Azure Portal.
   • TenantId: Set this to your Azure AD tenant identifier (GUID or domain name like 'contoso.onmicrosoft.com').
   • CallbackURL: Set this to the Redirect URI you specified in your app registration (e.g., http://localhost:33333 for desktop apps).

   Example connection string

   Profile=C:\profiles\Outlook.apip;AuthScheme=OAuth;InitiateOAuth=GETANDREFRESH;OAuthClientId=your_client_id;OAuthClientSecret=your_client_secret;TenantId=your_tenant_id;CallbackUrl=http://localhost:33333;
   

   
3. After saving the connection, select "Table or view" and select the table or view to export into Databricks, then close the CData Outlook Source Editor.

Configure the Databricks destination

With the Outlook 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.
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.
   
3. After saving the connection, select a table in the Use a Table menu and in the Action menu, select Insert.
4. On the Column Mappings tab, configure the mappings from the input columns to the destination columns.

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.