Skip to content

Commit 6a50293

Browse files
authored
Deleting duplicate word
1 parent f428932 commit 6a50293

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

articles/dms/includes/sql-virtual-machines-limitations.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -20,6 +20,6 @@ ms.author: mathoma
2020
- VM with SQL Server 2008 and below as target versions aren't supported when migrating to SQL Server on Azure Virtual Machines.
2121
- 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.
2222
- You must make sure the SQL IaaS Agent Extension in the target Azure Virtual Machine is in **Full mode** instead of Lightweight mode.
23-
- SQL IaaS Agent Extension only supports management of Default Server Server Instance or Single Named Instance,
23+
- SQL IaaS Agent Extension only supports management of Default Server Instance or Single Named Instance,
2424
- 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.
25-
- 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.
25+
- 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.

0 commit comments

Comments
 (0)