VOOZH about

URL: https://www.cdata.com/kb/tech/googledrive-ssis-task-lookup.rst

⇱ Use the CData SSIS Components to Insert New or Update Existing Google Drive Records from SQL Server


Use the CData SSIS Components to Insert New or Update Existing Google Drive Records from SQL Server

πŸ‘ Jerod Johnson
Jerod Johnson
Director, Technology Evangelism
Easily push SQL Server data to Google Drive using the CData SSIS Components. This example uses an SSIS workflow to either insert new records into Google Drive or update existing records with data from a SQL Server database.

SQL Server databases are commonly used to store enterprise records. It is often necessary to move this data to other locations. The CData SSIS Components for Google Drive allow you to easily transfer data from SQL Server to Google Drive.

This article demonstrates how to use the CData SSIS Components for Google Drive inside of a SQL Server Integration Services workflow to export data from SQL Server to Google Drive, utilizing a lookup component to find and update any existing records or insert new records.

Add the Components

To get started, add a new OLE DB source, CData Google Drive lookup, and two CData Google Drive destinations (one to handle a lookup with a match and one to handle a lookup without a match) to a new data flow task.

πŸ‘ OLD DB Source, CData Google Drive Lookup and CData Google Drive Destinations

Configure the OLE DB Source

Follow the steps below to specify properties required to connect to the SQL Server instance.

  1. Open the OLE DB Source and add a new connection. Enter your server and database information here.
  2. In the Data access mode menu, select "Table or view" and select the table or view to export into Google Drive. πŸ‘ The SQL Server table to export into Google Drive. (Salesforce is shown.)
  3. Close the OLE DB Source wizard and connect it to the CData Google Drive Destination.

Create a New Connection Manager for Google Drive

Follow the steps below to save connection properties in the Connection Manager.

  1. Create a new Connection manager: In the Connection Manager window, right-click and then click New Connection. The Add SSIS Connection Manager dialog is displayed.
  2. In the Connection Manager type menu, select the CData Google Drive Connection Manager.
  3. Configure the connection properties. A typical Google Drive connection requires:
    • User
    • Password
    • AccessToken
    πŸ‘ The Connection Manager. (Salesforce is shown.)

Configure the Google Drive Lookup

In the lookup component Transform Editor, define mappings from the SQL Server source table into the Google Drive lookup table.

  1. Double-click the Google Drive lookup to open the lookup component editor.
  2. In the Connection tab, select the Connection manager previously created.
  3. On the Connection tab, specify the Connection manager (or create a new one) and the table into which the data will be upserted. In this case, you will transfer Account records. πŸ‘ The table into which the data will be exported. (Salesforce is shown.)
  4. On the Columns tab, configure the mapping of the primary key from the input columns to the primary key of the lookup columns. πŸ‘ The mappings from SQL Server source to the SSIS lookup component. (Salesforce is shown.)

Configure the Google Drive Destinations

Using the lookup component, you know which entries from the data source already exist in Google Drive and which ones are new. Configure two Google Drive components to handle the situation where a match is found and a match is not found.

Lookup Match Destination

If the lookup component returns a match, update the existing record in Google Drive.

  1. Map the Lookup Match Output to a Google Drive destination component.
  2. Double-click the Google Drive destination to open the destination component editor.
  3. In the Connection Manager tab, select the Connection manager previously created.
  4. Specify the table which will be updated and set the Action to "Update." πŸ‘ The table which will be updated. (Salesforce is shown.)
  5. On the Column Mappings tab, configure the mappings from the input columns to the destination columns (be sure to map the SQL Server primary key column to the Google Drive primary key column). πŸ‘ The mappings from lookup component to the destination component. (Salesforce is shown.)

Lookup No Match Destination

If the lookup component does not return a match, add a new record to Google Drive.

  1. Map the Lookup No Match Output to a Google Drive destination component.
  2. Double-click the Google Drive destination to open the destination component editor.
  3. In the Connection Manager tab, select the Connection manager previously created.
  4. Specify the table into which the new record will be inserted and set the Action to "Insert." πŸ‘ The table into which the new record will be inserted. (Salesforce is shown.)
  5. On the Column Mappings tab, configure the mappings from the input columns to the destination columns. πŸ‘ The mappings from lookup component to the destination component. (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.

πŸ‘ The completed upsert. (Salesforce is shown.)

Ready to get started?

Download a free trial of the Google Drive SSIS Component to get started:

 Download Now

Learn more:

πŸ‘ Google Drive Icon
Google Drive SSIS Components

Powerful SSIS Source & Destination Components that allow you to easily connect SQL Server with live Google Drive data through SSIS Workflows.

Use the Google Drive Data Flow Components to access all kinds of data. Perfect for data synchronization, local back-ups, reporting, and more!