Back Up CleverPush data to SQL Server through SSIS

Jerod Johnson
Jerod Johnson
Director, Technology Evangelism
Effortlessly backup data to SQL Server by utilizing the CData API Driver for ADO.NET. In this article, we will employ an SSIS workflow to populate a database with CleverPush data data.

This article illustrates using the CleverPush ADO.NET Data Provider within a SQL Server SSIS workflow for the direct transfer of CleverPush data to a Microsoft SQL Server database. It's worth noting that the identical process detailed below is applicable to any CData ADO.NET Data Providers, enabling the direct connection of SQL Server with remote data through SSIS.

  1. Open Visual Studio and create a new Integration Services project.
  2. Add a new Data Flow task from the toolbox onto the Control Flow screen.
  3. In the Data Flow screen, add an ADO.NET Source and an OLE DB Destination from the toolbox.

    The components used in the data task in this example.
  4. Add a new connection and select .NET Providers\CData ADO.NET Provider for CleverPush.
  5. In the connection manager, enter the connection details for CleverPush data.

    Start by setting the Profile connection property to the location of the Cleverpush Profile on disk (e.g. C:\profiles\Cleverpush.apip). Next, set the ProfileSettings connection property to the connection string for Cleverpush (see below).

    Cleverpush API Profile Settings

    CleverPush uses private API keys to authenticate requests. Your API key is passed as the Authorization request header value on every API call.

    You can find your private API key in the CleverPush dashboard under Settings > API. Use the private key (not the public key) for server-side access.

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

    • AuthScheme: Set this to APIKey.
    • APIKey: Set this to your CleverPush private API key.

    Optional Connection Properties

    • ChannelId: Set this to your default CleverPush channel identifier. Most tables require a channel filter. Setting this property allows queries without specifying ChannelId in every WHERE clause.
    Connection properties in the Connection Manager dialog. (Salesforce is shown.)
  6. Open the DataReader editor and set the following information:

    • ADO.NET connection manager: In the Connection Managers menu, select the Data Connection you just created.
    • Data access mode: Select 'SQL command'.
    • SQL command text: In the DataReader Source editor, open the Component Properties tab and enter a SELECT command, such as the one below:
      SELECT Id, Name FROM Segments WHERE ChannelId = 'your_channel_id'
    The connection and query specified in the source component properties. (Salesforce is shown.)
  7. Close the DataReader editor and drag the arrow below the DataReader Source to connect it to the OLE DB Destination.
  8. Open the OLE DB Destination and enter the following information in the Destination Component Editor.

    • Connection manager: Add a new connection. Enter your server and database information here. In this example, SQLExpress is running on a separate machine.
    • Data access mode: Set your data access mode to "table or view" and select the table or view to populate in your database.
  9. Configure any properties you wish on the Mappings screen.

    Input and destination columns in the OLE DB Destination Editor.
  10. Close the OLE DB Destination Editor and run the project. After the SSIS task has finished executing, your database will be populated with data obtained from CleverPush data.

Ready to get started?

Connect to live data from CleverPush with the API Driver

Connect to CleverPush