You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
- 10,000 concurrent database migrations per service.
14
14
- Migration speed heavily depends on the target Azure SQL Database SKU and the self-hosted Integration Runtime host.
15
15
- Azure SQL Database migration scales poorly with table numbers due to ADF overhead in starting activities. If a database has thousands of tables, there will be a couple of seconds of startup time for each, even if they're composed of one row with 1 bit of data.
16
-
- Azure SQL Database table names with doublebyte characters currently aren't supported for migration. Mitigation is to rename tables before migration; they can be changed back to their original names after successful migration.
16
+
- Azure SQL Database table names with double-byte characters currently aren't supported for migration. Mitigation is to rename tables before migration; they can be changed back to their original names after successful migration.
17
17
- Tables with large blob columns may fail to migrate due to timeout.
18
18
- Database names with SQL Server reserved are currently not supported.
19
19
- Database names that include semicolons are currently not supported.
Copy file name to clipboardExpand all lines: articles/dms/includes/sql-managed-instance-limitations.md
+3-2Lines changed: 3 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -6,7 +6,7 @@ ms.date: 12/19/2022
6
6
ms.author: mathoma
7
7
---
8
8
9
-
- If migrating a single database, the database backups must be placed in a flat-file structure inside a database folder (including container root folder), and the folders can't be nested, as it's not supported.
9
+
- If migrating a single database, the database backups must be placed in a flat-file structure inside a database folder (including the container root folder), and the folders can't be nested, as it's not supported.
10
10
- If migrating multiple databases using the same Azure Blob Storage container, you must place backup files for different databases in separate folders inside the container.
11
11
- Overwriting existing databases using DMS in your target Azure SQL Managed Instance isn't supported.
12
12
- Configuring high availability and disaster recovery on your target to match source topology isn't supported by DMS.
@@ -17,4 +17,5 @@ ms.author: mathoma
17
17
- SSIS packages
18
18
- Server roles
19
19
- Server audit
20
-
- You can't use an existing self-hosted integration runtime created from Azure Data Factory for database migrations with DMS. Initially, the self-hosted integration runtime should be created using the Azure SQL migration extension in Azure Data Studio and can be reused for further database migrations.
20
+
- You can't use an existing self-hosted integration runtime created from Azure Data Factory for database migrations with DMS. Initially, the self-hosted integration runtime should be created using the Azure SQL migration extension in Azure Data Studio and can be reused for further database migrations.
21
+
- A single LRS job (created by DMS) can run for a maximum of 30 days. When this period expires, the job is automatically canceled thus your target database gets automatically deleted.
Copy file name to clipboardExpand all lines: articles/dms/includes/sql-virtual-machines-limitations.md
+5-5Lines changed: 5 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -2,7 +2,7 @@
2
2
author: MashaMSFT
3
3
ms.service: dms
4
4
ms.topic: include
5
-
ms.date: 12/19/2022
5
+
ms.date: 01/25/2023
6
6
ms.author: mathoma
7
7
---
8
8
@@ -20,8 +20,8 @@ ms.author: mathoma
20
20
21
21
- You can't use an existing self-hosted integration runtime created from Azure Data Factory for database migrations with DMS. Initially, the self-hosted integration runtime should be created using the Azure SQL migration extension in Azure Data Studio and can be reused for further database migrations.
22
22
- VM with SQL Server 2008 and below as target versions aren't supported when migrating to SQL Server on Azure Virtual Machines.
23
-
- If you're using VM with SQL Server 2012 or SQL Server 2014, you need to store your source database backup files on an Azure Storage Blob Container instead of using the network share option. Store the backup files as page blobs since block blobs are only supported in SQL 2016 and after.
24
-
- You must make sure the SQL IaaS Agent Extension in the target Azure Virtual Machine is in Full mode instead of Lightweight mode.
23
+
- If you're using a VM with SQL Server 2012 or SQL Server 2014, you need to store your source database backup files on an Azure Storage Blob Container instead of using the network share option. Store the backup files as page blobs since block blobs are only supported in SQL 2016 and after.
24
+
- You must make sure the SQL IaaS Agent Extension in the target Azure Virtual Machine is in **Full mode** instead of Lightweight mode.
25
25
- SQL IaaS Agent Extension only supports management of Default Server Server Instance or Single Named Instance,
26
-
- There is a temporary limit of 80 databases per target Azure Virtual Machine. A workaround to break the limit (reset the counter) is to Uninstall and Reinstall SQL IaaS Agent Extension in the target Azure Virtual Machine.
27
-
- Apart from configuring the Networking/Firewall of your Storage Account to allow your VM to access backup files, you also need to configure Networking/Firewall of your VM to allow outbound connection to your storage account.
26
+
- There is a temporary limit of 80 databases per target Azure Virtual Machine. A workaround to break the limit (reset the counter) is to Uninstall and Reinstall SQL IaaS Agent Extension in the target Azure Virtual Machine.
27
+
- Apart from configuring the Networking/Firewall of your Storage Account to allow your VM to access backup files, you also need to configure the Networking/Firewall of your VM to allow outbound connection to your storage account.
Copy file name to clipboardExpand all lines: articles/dms/index.yml
+49-46Lines changed: 49 additions & 46 deletions
Original file line number
Diff line number
Diff line change
@@ -4,9 +4,9 @@ summary: "Azure Database Migration Service enables seamless migrations from mult
4
4
metadata:
5
5
description: "Learn how to enable seamless migrations from multiple database sources to Azure Data platforms with minimal downtime by using Azure Database Migration Service."
6
6
keywords: azure database migration services, dms service, azure data migration, data migration service, database migration service
7
-
author: HJToland3
8
-
ms.author: jtoland
9
-
ms.date: 12/19/2019
7
+
author: croblesm
8
+
ms.author: roblescarlos
9
+
ms.date: 01/25/2022
10
10
ms.service: dms
11
11
ms.topic: landing-page
12
12
ms.custom: seo-azure-migrate, ignite-2022
@@ -26,61 +26,60 @@ landingContent:
26
26
url: migration-using-azure-data-studio.md
27
27
- text: Get Azure recommendation for migration using Azure Data Studio
28
28
url: ads-sku-recommend.md
29
+
- text: Migrate databases at scale using automation
0 commit comments