![]() |
VOOZH | about |
Using SQL Server as a backup for critical business data provides an essential safety net against loss. Backing up data to SQL Server enables business users to more easily connect that data with features like reporting, analytics, and more.
This example demonstrates how to use the CData SSIS Tasks for SendPulse inside of a SQL Server SSIS workflow to transfer SendPulse data into a Microsoft SQL Server database.
To get started, add a new SendPulse source and SQL Server ADO.NET destination to a new data flow task.
๐ The Data Flow task used in this example. (Salesforce is shown.)Follow the steps below to save SendPulse connection properties in a connection manager.
Start by setting the Profile connection property to the location of the SendPulse Profile on disk (e.g. C:\profiles\SendPulse.apip). Next, set the ProfileSettings connection property to the connection string for SendPulse (see below).
Log into your SendPulse account, navigate to Profile > Account Settings > API, and retrieve your API ID and Secret to use as your OAuth Client ID and Secret.
๐ Configuring a connection (Salesforce is shown).Follow the steps below to specify the query to be used to extract SendPulse data.
SELECT AutoresponderId, AutoresponderName FROM AutomationFlowsStatistics WHERE AutoresponderStatus = '1'๐ The SQL query to retrieve records. (Salesforce is shown.)
Follow the steps below to specify the SQL server table to load the SendPulse data into.
You can now run the project. After the SSIS Task has finished executing, your database will be populated with SendPulse data.
๐ The completed import. (Salesforce is shown.)Connect to live data from SendPulse with the API Driver
Connect to SendPulse