FastSpring Connector for Azure Data Factory (SSIS)

Read / write FastSpring data related to Orders, Subscriptions, Quotes, Products, Accounts and more without coding.
You can use this connector to integrate FastSpring data inside SSIS and SQL Server. Let's take a look at the steps below to see how exactly to accomplish that.

Download Documentation

If you are new with SSIS and ZappySys SSIS PowerPack then check below links to get started.

How to get started with SSIS and SSIS PowerPack. it covers how to install necessary tools to design/debug SSIS Packages, deploy to SSIS catalog and last Schedule SSIS Package to run using SQL Agent. It will also cover how to secure SSIS package and Parameterize values (e.g. Password, Hostname, etc).
SSIS API Source Help File
SSIS API Destination Help File

Connect to FastSpring in other apps

Connect to FastSpring in SSIS

Connect to FastSpring in SQL Server

Connect to FastSpring in Power BI

Connect to FastSpring in SSRS

Connect to FastSpring in Informatica

Connect to FastSpring in MS Access

Connect to FastSpring in MS Excel

Connect to FastSpring in SSAS

Connect to FastSpring in C#

Connect to FastSpring in Python

Connect to FastSpring in JAVA

Connect to FastSpring in Tableau

Connect to FastSpring in SAP Crystal Reports

Connect to FastSpring in Azure Data Factory (Pipeline)

Connect to FastSpring in Talend Studio

Connect to FastSpring in UiPath

Connect to FastSpring in PowerShell

Connect to FastSpring in ODBC

Create SSIS package

First of all, create an SSIS package, which will connect to FastSpring in SSIS. Once you do that, you are one step closer to deploying and running it in Azure-SSIS integration runtime in Azure Data Factory (ADF). Then simply proceed to the next step - creating and configuring Azure Blob Storage Container.

Prepare custom setup files for Azure-SSIS runtime

Now it's time to start preparing custom setup files for Azure-SSIS runtime. During Azure-SSIS runtime creation you can instruct ADF to perform a custom setup on a VM (Azure-SSIS node); i.e. to run the custom installer, copy files, execute PowerShell scripts, etc. In that case, your custom setup files are downloaded and run in the Azure-SSIS node (a VM) when you start the runtime. In this section we will prepare custom setup files so that you can run SSIS packages with SSIS PowerPack connectors inside in Azure-SSIS runtime.

Read more on Azure-SSIS runtime custom setup in Microsoft Azure Data Factory reference.

Trial Users

Use the step below if you are a Trial User, when you did not purchase a license key. Proceed with these steps:

Download SSIS PowerPack trial installer.
Make sure you don't rename the installer and keep it named as SSISPowerPackSetup_64bit_Trial.msi.
Create a text file and name it main.cmd (make it all lowercase, very important).

Copy and paste this script into it and save it:

set DIR=%CUSTOM_SETUP_SCRIPT_LOG_DIR%

echo Calling Step 1 : %TIME% >> "%DIR%\steps_log.txt"
dir /s /b > "%DIR%\file_list.txt"

echo Calling Step 2 : %TIME% >> "%DIR%\steps_log.txt"

::Install SSIS PowerPack
msiexec /i  "SSISPowerPackSetup_64bit_Trial.msi" ADDLOCAL=ALL /q  /L*V "%DIR%\powerpack_trial_install_log.txt"

echo Calling Step 3 : %TIME% >> "%DIR%\steps_log.txt"
dir "C:\Program Files\Microsoft SQL Server\*Zappy*.*"  /s /b >> "%DIR%\installed_files.txt"
dir "C:\Program Files (x86)\Microsoft SQL Server\*Zappy*.*"  /s /b >> "%DIR%\installed_files.txt"

echo DONE : %TIME% >> "%DIR%\steps_log.txt"

echo complete

This is the entry-point script that is executed when Azure-SSIS runtime is started.

At last! You are ready to upload these two files — main.cmd & SSISPowerPackSetup_64bit_Trial.msi — into your Azure Blob Storage container's folder, which we will do in the Upload custom setup files to Azure Blob Storage container step.

Paid Customers

Use the steps below if you are a Paid Customer, when you purchased a license. Proceed with these steps:

Download SSIS PowerPack paid installer.
Make sure you don't rename the installer and keep it named as SSISPowerPackSetup_64bit.msi.
Have your SSIS PowerPack license key handy, we will need it in the below script.
Create a text file and name it main.cmd (make it all lowercase, very important).
Copy and paste the below script into it.
Paste your license key by replacing parameter's --register argument with your real license key.

Finally, save main.cmd:

set DIR=%CUSTOM_SETUP_SCRIPT_LOG_DIR%

echo Calling Step 1 : %TIME% >> "%DIR%\steps_log.txt"
dir /s /b > "%DIR%\file_list.txt"

echo Calling Step 2 : %TIME% >> "%DIR%\steps_log.txt"

::Install SSIS PowerPack
msiexec /i  "SSISPowerPackSetup_64bit.msi" ADDLOCAL=ALL /q  /L*V "%DIR%\powerpack_install_log.txt"

echo Calling Step 3 : %TIME% >> "%DIR%\steps_log.txt"

::Activate PowerPack license (Optional)
"C:\Program Files (x86)\ZappySys\SSIS PowerPack (64 bit)\LicenseManager.exe" -p SSISPowerPack --register "lgGAAO0-----REPLACE-WITH-YOUR-LICENSE-KEY-----czM=" --logfile "%DIR%\powerpack_register_log.txt"

::Show System Info
echo Calling Step 4 : %TIME% >> "%DIR%\steps_log.txt"
"C:\Program Files (x86)\ZappySys\SSIS PowerPack (64 bit)\LicenseManager.exe" -i -l "%DIR%\sysinfo_log.txt"

echo Calling Step 5 : %TIME% >> "%DIR%\steps_log.txt"
dir "C:\Program Files\Microsoft SQL Server\*Zappy*.*"  /s /b >> "%DIR%\installed_files.txt"
dir "C:\Program Files (x86)\Microsoft SQL Server\*Zappy*.*"  /s /b >> "%DIR%\installed_files.txt"

echo DONE : %TIME% >> "%DIR%\steps_log.txt"

echo complete

This is the entry-point script that is executed when Azure-SSIS runtime is started.

At last! You are ready to upload these two files — main.cmd & SSISPowerPackSetup_64bit.msi — into your Azure Blob Storage container's folder, which we will do in the Upload custom setup files to Azure Blob Storage container step.

Upload custom setup files to Azure Blob Storage container

Within Azure Blob Storage container we will store custom setup files we prepared in the previous step so that Azure-SSIS can use them in custom setup process. Just perform these very simple, but very important steps:

Create Azure Blob Storage container, if you haven't done it already
Make sure you create and use Azure Blob Storage container instead of Azure Data Lake Storage folder. Azure Data Lake Storage won't allow creating an SAS URI for the container, which is a crucial step in the process.
Find Blob Containers node, right-click on it and hit Create Blob Container option:
Upload the two custom setup files — main.cmd & the MSI installer — into your Azure Blob Storage container's folder:
It was easy, wasn't it? It's time we create an SAS URI in the next step.

Create SAS URI for Azure Blob Container

Once you have custom setup files prepared, it's time we generate an SAS URI. This SAS URI will be used by a new Azure-SSIS runtime to install SSIS PowerPack inside the runtime's node, a VM. Let's proceed together by performing the steps below:

Install and launch Azure Storage Explorer.
Right-click on the Storage Accounts node and then hit Connect to Azure storage... menu item:
Proceed by right-clicking on that container node and select Get Shared Access Signature... option.
Next, set the Expiry time field to a date far in the future.
If you restart Azure-SSIS runtime and your SAS URI is expired by that time, it will not start.
Select Read, Create, Write, and List permissions:
We also recommend to add Delete permission too to support future functionality.
Copy SAS URL to the clipboard and save it for the next step: You can also generate and copy SAS URL from within Azure Portal itself:

Create Azure-SSIS integration runtime

Once you have the SAS URL we obtained in the previous step, we are ready to move on to create an Azure-SSIS runtime in Azure Data Factory:

Firstly, perform the steps described in Create an Azure-SSIS integration runtime article in Azure Data Factory reference.
In Advanced settings page section, configure Custom setup container SAS URI you obtained in the previous step:
And you are done! That was quick! You can see your Azure-SSIS runtime up and running:

The custom setup script is executed only once — at the time an Azure-SSIS runtime is started.

It is also executed if you stop and start Azure-SSIS runtime again.

Deploy SSIS package in Visual Studio

We are ready to deploy the SSIS package to Azure-SSIS runtime. Once you do that, proceed to the next step for the grand finale!

Execute SSIS package in SQL Server Management Studio (SSMS)

After all hard work, we are ready to execute SSIS package in SQL Server Management Studio (SSMS):

Connect to the SQL Server which is linked to your Azure-SSIS runtime and contains SSISDB database.
Navigate to Integration Services Catalog » Your Folder » Your Project » Your Package, right-click on it, and hit Execute...:
To view the status of the past execution, navigate to Integration Services Catalog » Your Folder » Your Project » Your Package, right-click on it, and select Reports » Standard Reports » All Executions menu item:

Scenarios

Moving SSIS PowerPack license to another Azure-SSIS runtime

If you are a Paid Customer, there will be a time when you no longer use Azure-SSIS runtime or you need to use your license on a different ADF instance. To transfer a license from one Azure-SSIS runtime to another, perform these steps:

Copy & paste this script into main.cmd we used in the previous step:

set DIR=%CUSTOM_SETUP_SCRIPT_LOG_DIR%

echo Calling Step 1 : %TIME% >> "%DIR%\steps_log.txt"
dir /s /b > "%DIR%\file_list.txt"
 
echo Calling Step 2 : %TIME% >> "%DIR%\steps_log.txt"

::Install SSIS PowerPack
msiexec /i  "SSISPowerPackSetup_64bit.msi" ADDLOCAL=ALL /q  /L*V "%DIR%\powerpack_install_log.txt"
 
echo Calling Step 3 : %TIME% >> "%DIR%\steps_log.txt"
 
::De-Activate same license
"C:\Program Files (x86)\ZappySys\SSIS PowerPack (64 bit)\LicenseManager.exe" -p SSISPowerPack --unregister --logfile "%DIR%\powerpack_un_register_log.txt"
 
::Show System Info
echo Calling Step 4 : %TIME% >> "%DIR%\steps_log.txt"
"C:\Program Files (x86)\ZappySys\SSIS PowerPack (64 bit)\LicenseManager.exe" -i -l "%DIR%\sysinfo_log.txt"
 
echo Calling Step 5 : %TIME% >> "%DIR%\steps_log.txt"
dir "C:\Program Files\Microsoft SQL Server\*Zappy*.*"  /s /b >> "%DIR%\installed_files.txt"
dir "C:\Program Files (x86)\Microsoft SQL Server\*Zappy*.*"  /s /b >> "%DIR%\installed_files.txt"
 
echo DONE : %TIME% >> "%DIR%\steps_log.txt"
 
echo complete

Start Azure-SSIS runtime.
This will unregister your license on the original Azure-SSIS runtime.
Stop Azure-SSIS runtime to deallocate resources in Azure.
Now you are free to activate it on another Azure-SSIS runtime.

Advanced topics

Actions supported by FastSpring Connector

FastSpring Connector support following actions for REST API integration. If some actions are not listed below then you can easily edit Connector file and enhance out of the box functionality.

Get Product IDs

[Read more...]

Get Products

[Read more...]

Get Products Publish Status

[Read more...]

Get Product

[Read more...]

Parameter	Description
Product Id

Create Product

[Read more...]

Update Product

[Read more...]

Get Product Prices

[Read more...]

Parameter	Description
Country Code
Currency Code

Get Order Items

[Read more...]

Get Order Items by OrderId

[Read more...]

Parameter	Description
Order Id

Get Orders

[Read more...]

Get Order by Id

[Read more...]

Parameter	Description
Order Id

Get Accounts

[Read more...]

Get Account Orders (For all accounts)

[Read more...]

Get Account Charges

[Read more...]

Get Account Orders (For a single account)

[Read more...]

Parameter	Description
Account Id

Get Account Charges by Id

[Read more...]

Parameter	Description
Account Id

Get Account By Id

[Read more...]

Parameter	Description
Account Id

Get Subscriptions Ids

[Read more...]

Get Subscriptions

[Read more...]

Get Subscription By Id

[Read more...]

Parameter	Description
Subscription Id

Get Quote By Id

[Read more...]

Parameter	Description
Quote Id

Get Quotes

[Read more...]

Get Subscription Report

[Read more...]

Parameter

Description

ReportColumns

Option	Value
activations	activations
arr	arr
average_mrr	average_mrr
buyer_email	buyer_email
buyer_id	buyer_id
cancellations	cancellations
chargeback_true_false	chargeback_true_false
company_id	company_id
company_name	company_name
country_iso	country_iso
country_name	country_name
coupon	coupon
customer_churn	customer_churn
discount	discount
driving_offer_type	driving_offer_type
driving_product_path	driving_product_path
item_id	item_id
lifetime_value	lifetime_value
mrr	mrr
mrr_decrease	mrr_decrease
mrr_downgrade	mrr_downgrade
mrr_growth_rate	mrr_growth_rate
mrr_increase	mrr_increase
mrr_paused	mrr_paused
mrr_resumed	mrr_resumed
mrr_upgrade	mrr_upgrade
new_subscribers	new_subscribers
occurred_date	occurred_date
order_id	order_id
product_display_name	product_display_name
product_id	product_id
product_name	product_name
product_path	product_path
purchase_type	purchase_type
return_true_false	return_true_false
revenue_churn	revenue_churn
store_id	store_id
store_name	store_name
subscriber_loss	subscriber_loss
subscribers	subscribers
subscription_period	subscription_period
subscription_period_end	subscription_period_end
subscription_period_start	subscription_period_start
subscription_start_date	subscription_start_date
subscription_status	subscription_status
subscription_true_false	subscription_true_false
subscriptions	subscriptions
sync_date	sync_date
transaction_currency	transaction_currency
transaction_date	transaction_date
transaction_month	transaction_month
transaction_type	transaction_type
transaction_year	transaction_year

GroupByColumns

Option	Value
buyer_email	buyer_email
buyer_id	buyer_id
chargeback_true_false	chargeback_true_false
company_id	company_id
company_name	company_name
country_iso	country_iso
country_name	country_name
coupon	coupon
discount	discount
driving_offer_type	driving_offer_type
driving_product_path	driving_product_path
item_id	item_id
occurred_date	occurred_date
order_id	order_id
product_display_name	product_display_name
product_id	product_id
product_name	product_name
product_path	product_path
purchase_type	purchase_type
return_true_false	return_true_false
store_id	store_id
store_name	store_name
subscription_period	subscription_period
subscription_period_end	subscription_period_end
subscription_period_start	subscription_period_start
subscription_start_date	subscription_start_date
subscription_status	subscription_status
subscription_true_false	subscription_true_false
sync_date	sync_date
transaction_currency	transaction_currency
transaction_date	transaction_date
transaction_month	transaction_month
transaction_type	transaction_type
transaction_year	transaction_year

Get Revenue Report

[Read more...]

Parameter

Description

ReportColumns

Option	Value
Buyer_Email	Buyer_Email
Buyer_ID	Buyer_ID
Chargeback_True_False	Chargeback_True_False
Company_ID	Company_ID
Company_Name	Company_Name
Country_ISO	Country_ISO
Country_Name	Country_Name
CouponDigital_Backup_Fulfillment_Fee	CouponDigital_Backup_Fulfillment_Fee
Digital_Backup_Fulfillment_Fee_in_USD	Digital_Backup_Fulfillment_Fee_in_USD
Digital_Fulfillment_Fee	Digital_Fulfillment_Fee
Digital_Fulfillment_Fee_in_USD	Digital_Fulfillment_Fee_in_USD
Discount	Discount
Driving_Offer_TypeDriving_Product_Path	Driving_Offer_TypeDriving_Product_Path
Fixed_FeeFixed_Fee_in_USDIncomeIncome_in_USDItem_ID	Fixed_FeeFixed_Fee_in_USDIncomeIncome_in_USDItem_ID
Order_ID	Order_ID
Physical_Backup_Fulfillment_Fee	Physical_Backup_Fulfillment_Fee
Physical_Backup_Fulfillment_Fee_in_USD	Physical_Backup_Fulfillment_Fee_in_USD
Product_Display_Name	Product_Display_Name
Product_ID	Product_ID
Product_Name	Product_Name
Product_Path	Product_Path
Purchase_Type	Purchase_Type
Return_Fee	Return_Fee
Return_Fee_in_USD	Return_Fee_in_USD
Return_True_False	Return_True_False
SegmentStore_Chargeback_Fee	SegmentStore_Chargeback_Fee
Store_ID	Store_ID
Store_Name	Store_Name
Subscription_Period	Subscription_Period
Subscription_Period_End	Subscription_Period_End
Subscription_Period_Start	Subscription_Period_Start
Subscription_Start_Date	Subscription_Start_Date
Subscription_Status	Subscription_Status
Subscription_True_False	Subscription_True_False
Tax	Tax
Tax_Fee	Tax_Fee
Tax_Fee_in_USD	Tax_Fee_in_USD
Tax_in_USD	Tax_in_USD
Transaction_Amount	Transaction_Amount
Transaction_Amount_in_USD	Transaction_Amount_in_USD
Transaction_Currency	Transaction_Currency
Transaction_Date	Transaction_Date
Transaction_Fee	Transaction_Fee
Transaction_Fee_in_USD	Transaction_Fee_in_USD
Transaction_Item_Count	Transaction_Item_Count
Transaction_Month	Transaction_Month
Transaction_Rate	Transaction_Rate
Transaction_Time_UTC	Transaction_Time_UTC
Transaction_Type	Transaction_Type
Transaction_Year	Transaction_Year
Grand_Total_In_USD	Grand_Total_In_USD
syncDatecountryISO	syncDatecountryISO
Product_Count	Product_Count
Product_Units	Product_Units

GroupByColumns

Option	Value
Buyer_Email	Buyer_Email
Buyer_ID	Buyer_ID
Chargeback_True_False	Chargeback_True_False
Company_ID	Company_ID
Company_Name	Company_Name
Country_ISO	Country_ISO
Country_Name	Country_Name
Coupon	Coupon
Discount	Discount
Driving_Offer_Type	Driving_Offer_Type
Driving_Product_Path	Driving_Product_Path
Income	Income
Item_ID	Item_ID
Order_ID	Order_ID
Product_Display_Name	Product_Display_Name
Product_ID	Product_ID
Product_Name	Product_Name
Product_Path	Product_Path
Purchase_Type	Purchase_Type
Return_True_False	Return_True_False
Segment	Segment
Store_ID	Store_ID
Store_Name	Store_Name
Subscription_Period	Subscription_Period
Subscription_Status	Subscription_Status
Subscription_True_False	Subscription_True_False
Transaction_Currency	Transaction_Currency
Transaction_Date	Transaction_Date
Transaction_Month	Transaction_Month
Transaction_Type	Transaction_Type
Transaction_Year	Transaction_Year
countryISO	countryISO

Generic Request

This is generic endpoint. Use this endpoint when some actions are not implemented by connector. Just enter partial URL (Required), Body, Method, Header etc. Most parameters are optional except URL. [Read more...]

Parameter	Description
Url	API URL goes here. You can enter full URL or Partial URL relative to Base URL. If it is full URL then domain name must be part of ServiceURL or part of TrustedDomains
Body	Request Body content goes here
IsMultiPart	Set this option if you want to upload file(s) (i.e. POST RAW file data) or send data using Multi-Part encoding method (i.e. Content-Type: multipart/form-data). Multi-Part request allows you to mix key/value and upload files in same request. On the other hand raw upload allows only single file upload (without any key/value) ==== Raw Upload (Content-Type: application/octet-stream) ===== To upload single file in raw mode check this option and specify full file path starting with @ sign in the Body (e.g. @c:\data\myfile.zip ) ==== Form-Data / Multipart Upload (Content-Type: multipart/form-data) ===== To treat your Request data as multi part fields you must specify key/value pairs separated by new lines into RequestData field (i.e. Body). Each key value pair is entered on new-line and key/value are separated using equal sign (=). Preceding and trailing spaces are ignored also blank lines are ignored. If field value has some any special character(s) then use escape sequence (e.g. For NewLine: \r\n, For Tab: \t, For at (@): \@). When value of any field starts with at sign (@) its automatically treated as File you want to upload. By default file content type is determined based on extension however you can supply content type manually for any field using this way [ YourFileFieldName.Content-Type=some-content-type ]. By default File Upload Field always includes Content-Type in the request (non file fields do not have content-type by default unless you supply manually). For some reason if you dont want to use Content-Type header in your request then supply blank Content-Type to exclude this header altogather [e.g. SomeFieldName.Content-Type= ]. In below example we have supplied Content-Type for file2 and SomeField1, all other fields are using default content-type. See below Example of uploading multiple files along with additional fields. If some API requires you to pass Content-Type: multipart/form-data rather than multipart/form-data then manually set Request Header => Content-Type: multipart/mixed (it must starts with multipart/ else will be ignored). file1=@c:\data\Myfile1.txt file2=@c:\data\Myfile2.json file2.Content-Type=application/json SomeField1=aaaaaaa SomeField1.Content-Type=text/plain SomeField2=12345 SomeFieldWithNewLineAndTab=This is line1\r\nThis is line2\r\nThis is \ttab \ttab \ttab SomeFieldStartingWithAtSign=\@MyTwitterHandle
Filter	Enter filter to extract array from response. Example: $.rows[] --OR-- $.customers[].orders[*]. Check your response document and find out hierarchy you like to extract
Headers	Headers for Request. To enter multiple headers use double pipe or new line after each {header-name}:{value} pair

Conclusion

In this article we discussed how to connect to FastSpring in Azure Data Factory (SSIS) and integrate data without any coding. Click here to Download FastSpring Connector for Azure Data Factory (SSIS) and try yourself see how easy it is. If you still have any question(s) then ask here or simply click on live chat icon below and ask our expert (see bottom-right corner of this page).

Download FastSpring Connector for Azure Data Factory (SSIS) Documentation

More integrations

Other application integration scenarios for FastSpring

SSIS

SQL Server

Power BI

SSRS

Informatica

MS Access

MS Excel

SSAS

Python

JAVA

Tableau

SAP Crystal Reports

Azure Data Factory (Pipeline)

Talend Studio

UiPath

PowerShell

ODBC

Other connectors for Azure Data Factory (SSIS)

Amazon Ads

Amazon MWS

Amazon Selling Partner (SP-API)

Asana

Azure DevOps

Cosmos DB

DropBox

FastSpring

Google Drive

Hubspot

Jira

Mailchimp

ManagedEngine ServiceDesk Plus (Zoho)

Nativo

OData

OneDrive

Outlook Mail (Office 365)

Power BI

ServiceNow

SharePoint Online

Shopify

Smartsheet

Stripe

YouTube

Zendesk

Zoho CRM

Zoho SalesIQ

Zoom

REST API

JSON

JSON File

XML

SOAP

XML File

JDBC-ODBC Bridge

Salesforce

CSV

Amazon S3 JSON File

Amazon S3 XML File

Amazon S3 CSV File

Azure Blob JSON File

Azure Blob XML File

Azure Blob CSV File

FTP/SFTP JSON File

FTP/SFTP XML File

FTP/SFTP CSV File

Build your own Custom API Connector

Download FastSpring Connector for Azure Data Factory (SSIS) Documentation

Common Searches:

How to connect FastSpring in Azure Data Factory (SSIS)?
How to get FastSpring data in Azure Data Factory (SSIS)?
How to read FastSpring data in Azure Data Factory (SSIS)?
How to load FastSpring data in Azure Data Factory (SSIS)?
How to import FastSpring data in Azure Data Factory (SSIS)?
How to pull FastSpring data in Azure Data Factory (SSIS)?
How to push data to FastSpring in Azure Data Factory (SSIS)?
How to write data to FastSpring in Azure Data Factory (SSIS)?
How to POST data to FastSpring in Azure Data Factory (SSIS)?
Call FastSpring API in Azure Data Factory (SSIS)
Consume FastSpring API in Azure Data Factory (SSIS)
FastSpring Azure Data Factory (SSIS) Automate
FastSpring Azure Data Factory (SSIS) Integration
Integration FastSpring in Azure Data Factory (SSIS)
Consume real-time FastSpring data in Azure Data Factory (SSIS)
Consume real-time FastSpring API data in Azure Data Factory (SSIS)
FastSpring ODBC Driver | ODBC Driver for FastSpring | ODBC FastSpring Driver | SSIS FastSpring Source | SSIS FastSpring Destination
Connect FastSpring in Azure Data Factory (SSIS)
Load FastSpring in Azure Data Factory (SSIS)
Load FastSpring data in Azure Data Factory (SSIS)
Read FastSpring data in Azure Data Factory (SSIS)
FastSpring API Call in Azure Data Factory (SSIS)