![]() |
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 Omnisend inside of a SQL Server SSIS workflow to transfer Omnisend data into a Microsoft SQL Server database.
To get started, add a new Omnisend 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 Omnisend connection properties in a connection manager.
Start by setting the Profile connection property to the location of the Omnisend Profile on disk (e.g. C:\profiles\Omnisend.apip). Next, set the ProfileSettings connection property to the connection string for Omnisend (see below).
Navigate to your Omnisend account integrations at https://app.omnisend.com/#/my-account/integrations/api-keys to generate an API key.
๐ Configuring a connection (Salesforce is shown).Follow the steps below to specify the query to be used to extract Omnisend data.
SELECT BatchId, Method FROM Batches WHERE Status = 'completed'๐ The SQL query to retrieve records. (Salesforce is shown.)
Follow the steps below to specify the SQL server table to load the Omnisend data into.
You can now run the project. After the SSIS Task has finished executing, your database will be populated with Omnisend data.
๐ The completed import. (Salesforce is shown.)Connect to live data from Omnisend with the API Driver
Connect to Omnisend