Two-Activity chained Data Factory Pipeline

Azure Public Test Date Azure Public Test Result

Azure US Gov Last Test Date Azure US Gov Last Test Result

Best Practice Check Cred Scan Check

Deploy to Azure Deploy To Azure US Gov Visualize

This template deploys a new Data Factory and requisite objects (linked services, datasets, pipelines, gateways, etc.) to fascilitate a two-activity chained Data Factory pipeline. The first leg of the pipeline leverages data management gateway to pull data from an on-premises SQL server source into Azure Data Lake Store in Apache orc columnar storage format. The second leg of the pipeline pulls data from orc files in Azure Data Lake Store and inserts into Azure SQL as a final destination. This pipeline can be easily customized to accommodated a wide variety of additional sources and targets.

Pipeline Image

Please complete the following steps before deploying the template:

  1. This example leverages a single table in the AdventureWorks2014 (OLTP) database for demonstration purposes. Before running this template make sure that you've restored this database to an on-premises SQL server (source) as well as an Azure SQL Server instance (destination).
  2. Make sure that you've opened up the required ports to allow communication between data management gateway and Azure. Details on these requirements can be found here.
  3. Create an Azure Data Lake Store leveraging the portal, ARM template, CLI, etc.
  4. Configure service principal authentication so that Data Factory can access your Data Lake Store using the following Data Lake Store connector instructions. Be sure to retain the Application ID and Key as you'll need these for the ARM template parameters.

Deploying The Template

You can deploy this sample directly through the Azure Portal or by using the scripts supplied in the root of the repository.

To deploy a sample using the Azure Portal, click the Deploy to Azure button at the top of the article.

To deploy the sample via the command line (using Azure PowerShell or the Azure CLI) you can use the scripts.

Simply execute the script from the root folder and pass in the folder name of the sample (101-data-factory-blob-to-sql-copy-stored-proc). For example:

.\Deploy-AzureResourceGroup.ps1 -ResourceGroupLocation 'eastus' -ArtifactStagingDirectory 101-data-factory-blob-to-sql-copy-stored-proc -a 101-data-factory-blob-to-sql-copy-stored-proc -l eastus

After Deploying the Template:

  1. Install Data Management Gateway on-premises using these instructions.
  2. Register data management gateway w/ ADF by inputing the key from the Azure Data Factory portal.
  3. Encrypt the connection string for your on-premises database using the New-AzureRmDataFactoryEncryptValue command from the AzureRM.DataFactories PowerShell module. This will ensure that you're on-premises data store credentials are encrypted using the key from data management gateway.
  4. Replace the placeholder connectionString value in your SqlLinkedService linked service with the encrypted value created above by editing the linked service in the Data Factory console's "Author and deploy" blade. This password will be encrypted using an ADF managed key.
  5. Un-pause data pipeline from the ADF Monitor and Manage console.
  6. Test your new pipline out by inserting a new record into the Sales.Currency table in your on-premises database. Make sure to set the timestamp to a time that falls within an upcoming ADF data slice.

Tags: Microsoft.DataFactory/datafactories, gateways, linkedservices, AzureDataLakeStore, OnPremisesSqlServer, AzureSqlDatabase, datasets, string, Datetime, OrcFormat, SqlServerTable, AzureSqlTable, dataPipelines, Copy, SqlSource, AzureDataLakeStoreSink, AzureDataLakeStoreSource, SqlSink, TabularTranslator