Migrate SQL Server Agent jobs to ADF with SSMS
APPLIES TO: Azure Data Factory Azure Synapse Analytics
When migrating on-premises SQL Server Integration Services (SSIS) workloads to SSIS in ADF, after SSIS packages are migrated, you can do batch migration of SQL Server Agent jobs with job step type of SQL Server Integration Services Package to Azure Data Factory (ADF) pipelines/activities/schedule triggers via SQL Server Management Studio (SSMS) SSIS Job Migration Wizard.
In general, for selected SQL agent jobs with applicable job step types, SSIS Job Migration Wizard can:
- map on-premises SSIS package location to where the packages are migrated to, which are accessible by SSIS in ADF.
Package location of File System is supported only.
- migrate applicable jobs with applicable job steps to corresponding ADF resources as below:
|SQL Agent job object||ADF resource||Notes|
|SQL Agent job||pipeline||Name of the pipeline will be Generated for <job name>.
Built-in agent jobs are not applicable:
|SSIS job step||Execute SSIS package activity|
|schedule||schedule trigger||Name of the schedule trigger will be Generated for <schedule name>.
Below options in SQL Agent job schedule will be ignored in migration:
Below are the differences after SQL Agent job schedule is migrated to ADF schedule trigger:
- generate Azure Resource Manager (ARM) templates in local output folder, and deploy to data factory directly or later manually. For more information about ADF Resource Manager templates, see Microsoft.DataFactory resource types.
The feature described in this article requires SQL Server Management Studio version 18.5 or higher. To get the latest version of SSMS, see Download SQL Server Management Studio (SSMS).
Migrate SSIS jobs to ADF
In SSMS, in Object Explorer, select SQL Server Agent, select Jobs, then right-click and select Migrate SSIS Jobs to ADF.
Sign In Azure, select Azure Subscription, Data Factory, and Integration Runtime. Azure Storage is optional, which is used in the package location mapping step if SSIS jobs to be migrated have SSIS File System packages.
Map the paths of SSIS packages and configuration files in SSIS jobs to destination paths where migrated pipelines can access. In this mapping step, you can:
- Select a source folder, then Add Mapping.
- Update source folder path. Valid paths are folder paths or parent folder paths of packages.
- Update destination folder path. Default is relative path to the default Storage account, which is selected in step 1.
- Delete a selected mapping via Delete Mapping.
Select applicable jobs to migrate, and configure the settings of corresponding Executed SSIS Package activity.
Default Setting, applies to all selected steps by default. For more information of each property, see Settings tab for the Execute SSIS Package activity when package location is File System (Package).
Step Setting, configure setting for a selected step.
Apply Default Setting: default is selected. Unselect to configure setting for selected step only.
For more information of other properties, see Settings tab for the Execute SSIS Package activity when package location is File System (Package).
Generate and deploy ARM template.
- Select or input the output path for the ARM templates of the migrated ADF pipelines. Folder will be created automatically if not exists.
- Select the option of Deploy ARM templates to your data factory:
- Default is unselected. You can deploy generated ARM templates later manually.
- Select to deploy generated ARM templates to data factory directly.
Migrate, then check results.
Submit and view feedback for