Migrate SQL Server Agent jobs to ADF with SSMS

  • Article

APPLIES TO: Azure Data Factory Azure Synapse Analytics

Tip

Try out Data Factory in Microsoft Fabric, an all-in-one analytics solution for enterprises. Microsoft Fabric covers everything from data movement to data science, real-time analytics, business intelligence, and reporting. Learn how to start a new trial for free!

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.

    Note

    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 Server Maintenance Job
  • syspolicy_purge_history
  • collection_set_*
  • mdw_purge_data_*
  • sysutility_*
    		•
    SSIS job step Execute SSIS package activity
  • Name of the activity will be <step name>.
  • Proxy account used in job step will be migrated as Windows authentication of this activity.
  • Execution options except Use 32-bit runtime defined in job step will be ignored in migration.
  • Verification defined in job step will be ignored in migration.
    		•
    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:
  • Second-level interval.
  • Start automatically when SQL Server Agent starts
  • Start whenever the CPUs become idle
  • weekday and weekend day time zone
    Below are the differences after SQL Agent job schedule is migrated to ADF schedule trigger:
  • ADF Schedule Trigger subsequent run is independent of the execution state of the antecedent triggered run.
  • ADF Schedule Trigger recurrence configuration differs from Daily frequency in SQL agent job.
    		•
    • 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.

    Prerequisites

    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

    1. In SSMS, in Object Explorer, select SQL Server Agent, select Jobs, then right-click and select Migrate SSIS Jobs to ADF. Screenshot shows SQL Server Management Studio Object Explorer, where you can select Jobs, then Migrate S S I S Jobs to A D F.

    2. 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. menu

    3. 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:

      1. Select a source folder, then Add Mapping.
      2. Update source folder path. Valid paths are folder paths or parent folder paths of packages.
      3. Update destination folder path. Default is relative path to the default Storage account, which is selected in step 1.
      4. Delete a selected mapping via Delete Mapping. Screenshot shows the Map S S I S Package and Configuration Paths page, where you can add mapping. Screenshot shows the Map S S I S Package and Configuration Paths page, where you can update the source and destination folder paths.

    4. 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). Screenshot shows the Select S S I S Jobs page, where you can configure the settings of corresponding Executed SSIS Package activity.

      • 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). Screenshot shows the Select S S I S Jobs page, where you can apply the default settings.

    5. Generate and deploy ARM template.

      1. Select or input the output path for the ARM templates of the migrated ADF pipelines. Folder will be created automatically if not exists.
      2. 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. Screenshot shows the Configure Migration page, where you can select or input the output path for the ARM templates of the migrated ADF pipelines and select the option of Deploy ARM templates to your data factory.

    6. Migrate, then check results. Screenshot shows the Migration Result page, which displays the progress of the migration.

    Related content

    Run and monitor pipeline