Skip to content

Commit 704e024

Browse files
authored
Merge pull request #104028 from prmadhes-msft/patch-1
Limitation in ADS migration activity
2 parents 957cbf2 + 696013e commit 704e024

File tree

1 file changed

+2
-0
lines changed

1 file changed

+2
-0
lines changed

articles/dms/migration-using-azure-data-studio.md

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -160,6 +160,8 @@ To monitor database migrations in the Azure portal:
160160

161161
- You can't use an existing self-hosted integration runtime that was created in Azure Data Factory for database migrations with Database Migration Service. Initially, create the self-hosted integration runtime by using the Azure SQL Migration extension for Azure Data Studio. You can reuse that self-hosted integration runtime in future database migrations.
162162

163+
- Azure Data Studio currently supports both Azure Active Directory (Azure AD)/Windows authentication and SQL logins for connecting to the source SQL Server instance. For the Azure SQL targets, only SQL logins are supported.
164+
163165
## Pricing
164166

165167
- Azure Database Migration Service is free to use with the Azure SQL Migration extension for Azure Data Studio. You can migrate multiple SQL Server databases by using Database Migration Service at no charge.

0 commit comments

Comments
 (0)