![]() |
VOOZH | about |
This article illustrates using the Omnisend ADO.NET Data Provider within a SQL Server SSIS workflow for the direct transfer of Omnisend 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.
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.In the connection manager, enter the connection details for Omnisend data.
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.
👁 Connection properties in the Connection Manager dialog. (Salesforce is shown.)Open the DataReader editor and set the following information:
SELECT BatchId, Method FROM Batches WHERE Status = 'completed'
Open the OLE DB Destination and enter the following information in the Destination Component Editor.
Configure any properties you wish on the Mappings screen.
👁 Input and destination columns in the OLE DB Destination Editor.Connect to live data from Omnisend with the API Driver
Connect to Omnisend