Skip to content

Commit 16a9df1

Browse files
authored
Clarification on SSISDB migration
Wording leads to understand that DMS can migrate SSISDB database, rather than packages contained in it.
1 parent e1dc657 commit 16a9df1

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

articles/data-factory/scenario-ssis-migration-ssisdb-mi.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -16,9 +16,9 @@ When migrating database workloads from a SQL Server instance to Azure SQL Manage
1616

1717
This article focuses on the migration of SQL Server Integration Service (SSIS) packages stored in SSIS catalog (SSISDB) and SQL Server Agent jobs that schedule SSIS package executions.
1818

19-
## Migrate SSIS catalog (SSISDB)
19+
## Migrate packages in SSIS catalog (SSISDB)
2020

21-
SSISDB migration can be done using DMS, as described in the article:
21+
DMS can migrate SSIS packages stored in SSISDB, as described in the article:
2222
[Migrate SSIS packages to SQL Managed Instance](../dms/how-to-migrate-ssis-packages-managed-instance.md).
2323

2424
## SSIS jobs to SQL Managed Instance agent
@@ -38,4 +38,4 @@ Since a migration tool for SSIS jobs is not yet available, they have to be migra
3838
## Next steps
3939

4040
- [Connect to SSISDB in Azure](/sql/integration-services/lift-shift/ssis-azure-connect-to-catalog-database)
41-
- [Run SSIS packages deployed in Azure](/sql/integration-services/lift-shift/ssis-azure-run-packages)
41+
- [Run SSIS packages deployed in Azure](/sql/integration-services/lift-shift/ssis-azure-run-packages)

0 commit comments

Comments
 (0)