Merge pull request #231602 from croblesm/crobles-0320-misc-updates

PMEds28 · web-flow · commit b78349c5ccd0 · 2023-03-22T07:26:15.000Z
Updating known issues, SKU recommendations and more.
diff --git a/articles/dms/dms-tools-matrix.md b/articles/dms/dms-tools-matrix.md
diff --git a/articles/dms/includes/sql-database-limitations.md b/articles/dms/includes/sql-database-limitations.md
@@ -1,7 +1,7 @@
 ---
 author: croblesm
 ms.author: roblescarlos
-ms.date: 01/25/2023
+ms.date: 03/21/2023
 ms.service: dms
 ms.topic: include
 ---
@@ -12,9 +12,9 @@ Azure SQL Database offline migration utilizes Azure Data Factory (ADF) pipelines
 - 100,000 table per database limit.
 - 10,000 concurrent database migrations per service.
 - Migration speed heavily depends on the target Azure SQL Database SKU and the self-hosted Integration Runtime host.
-- 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.
+- Azure SQL Database migration scales poorly with table numbers due to ADF overhead in starting activities. If a database has thousands of tables, the startup process of each table might take a couple of seconds, even if they're composed of one row with 1 bit of data.
 - 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.
 - Tables with large blob columns may fail to migrate due to timeout.
 - Database names with SQL Server reserved are currently not supported.
 - Database names that include semicolons are currently not supported.
-- Computed columns do not get migrated.
+- Computed columns don't get migrated.
diff --git a/articles/dms/includes/sql-managed-instance-limitations.md b/articles/dms/includes/sql-managed-instance-limitations.md
@@ -1,19 +1,20 @@
 ---
 author: croblesm
 ms.author: roblescarlos
-ms.date: 12/19/2022
+ms.date: 03/21/2022
 ms.service: dms
 ms.topic: include
 ---
 
 - 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.
 - 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.
 - Overwriting existing databases using DMS in your target Azure SQL Managed Instance isn't supported.
-- Configuring high availability and disaster recovery on your target to match source topology isn't supported by DMS.
+- DMS doesn't support configuring high availability and disaster recovery on your target to match the source topology.
 - The following server objects aren't supported:
    - SQL Server Agent jobs
    - Credentials
    - SSIS packages
    - Server audit
 - 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.
 - 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.
+- If you received the following error: `Memory-optimized filegroup must be empty in order to be restored on General Purpose tier of SQL Database Managed Instance`. This issue is by design, Hekaton (**also known as SQL Server In-Memory OLTP**) isn't supported on General Purpose tier of Azure SQL Managed Instance. To continue migration, one way is to upgrade to Business Critical tier, which supports Hekaton. Another way is to make sure the source database isn't using it while the Azure SQL Managed Instance is General Purpose.
diff --git a/articles/dms/includes/sql-virtual-machines-limitations.md b/articles/dms/includes/sql-virtual-machines-limitations.md
@@ -1,7 +1,7 @@
 ---
 author: croblesm
 ms.author: roblescarlos
-ms.date: 01/25/2023
+ms.date: 03/21/2023
 ms.service: dms
 ms.topic: include
 ---
@@ -15,11 +15,14 @@ ms.topic: include
    - Credentials
    - SSIS packages
    - Server audit
-
 - 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.
 - VM with SQL Server 2008 and below as target versions aren't supported when migrating to SQL Server on Azure Virtual Machines.
 - 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.
 - You must make sure the SQL IaaS Agent Extension in the target Azure Virtual Machine is in **Full mode** instead of Lightweight mode.
 - SQL IaaS Agent Extension  only supports management of Default Server Instance or Single Named Instance,
 - 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.
-- 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.
+- Apart from configuring the Networking/Firewall of your Azure Storage Account to allow your VM to access backup files. You also need to configure the Networking/Firewall of your SQL Server on Azure VM to allow outbound connection to your storage account.
+- You need to keep the target SQL Server on Azure VM **power ON** while the SQL Migration is in progress. Also, when creating a new migration, failover or cancel the migration.
+- **Error**: `Login failed for user 'NT Service\SQLIaaSExtensionQuery`. 
+**Reason**: SQL Server instance is in single-user mode. One possible reason is the target SQL Server on Azure VM is in upgrade mode. **Solution**: Please wait for the target SQL Server on Azure VM exit the upgrade mode and start migration again. 
+- **Error**: `Ext_RestoreSettingsError, message: Failed to create restore job.;Cannot create file 'F:\data\XXX.mdf' because it already exists`. **Solution**: Connect to the target SQL Server on Azure VM  and delete the XXX.mdf file. Then, start migration again. 
diff --git a/articles/dms/known-issues-azure-sql-migration-azure-data-studio.md b/articles/dms/known-issues-azure-sql-migration-azure-data-studio.md
@@ -4,7 +4,7 @@ titleSuffix: Azure Database Migration Service
 description: Known issues, limitations and troubleshooting guide for Azure SQL Migration extension for Azure Data Studio
 author: croblesm
 ms.author: roblescarlos
-ms.date: 01/05/2023
+ms.date: 03/14/2023
 ms.service: dms
 ms.topic: troubleshooting
 ms.custom: seo-lt-2019
@@ -30,9 +30,9 @@ Known issues and troubleshooting steps associated with the Azure SQL Migration e
 
 - **Message**: `Migration for Database 'DatabaseName' failed with error cannot find server certificate with thumbprint.`
 
-- **Cause**: The source database is protected with Transparent Data Encryption (TDE). You need to migrate the Database Encryption Key (DEK) to the target Azure SQL Managed Instance or SQL Server on Azure Virtual Machine before starting the migration.
+- **Cause**: Before migrating data, you need to migrate the certificate of the source SQL Server instance from a database that is protected by Transparent Data Encryption (TDE) to the target Azure SQL Managed Instance or SQL Server on Azure Virtual Machine.
 
-- **Recommendation**: Migrate the TDE certificate to the target instance and retry the process. For more information about migrating TDE-enabled databases, see [Tutorial: Migrate TDE-enabled databases (preview) to Azure SQL in Azure Data Studio](./tutorial-transparent-data-encryption-migration-ads.md).  
+- **Recommendation**: Migrate the TDE certificate to the target instance and retry the process. For more information about migrating TDE-enabled databases, see [Tutorial: Migrate TDE-enabled databases (preview) to Azure SQL in Azure Data Studio](/azure/dms/tutorial-transparent-data-encryption-migration-ads).  
 
 
 - **Message**: `Migration for Database <DatabaseName> failed with error 'Non retriable error occurred while restoring backup with index 1 - 3169 The database was backed up on a server running version %ls. That version is incompatible with this server, which is running version %ls. Either restore the database on a server that supports the backup, or use a backup that is compatible with this server.`
@@ -82,15 +82,26 @@ Known issues and troubleshooting steps associated with the Azure SQL Migration e
 
 - **Recommendation**: If migrating multiple databases to **Azure SQL Managed Instance** using the same Azure Blob Storage container, you must place backup files for different databases in separate folders inside the container. For more information about LRS, see [Migrate databases from SQL Server to SQL Managed Instance by using Log Replay Service (Preview)](/azure/azure-sql/managed-instance/log-replay-service-migrate#limitations).
 
+- **Message**: `Migration for Database <Database Name> failed with error 'Non retriable error occurred while restoring backup with index 1 - 12824 The sp_configure value 'contained database authentication' must be set to 1 in order to restore a contained database.  You may need to use RECONFIGURE to set the value_in_use.
+RESTORE DATABASE is terminating abnormally.`
 
-    > [!NOTE]
-    > For more information on general troubleshooting steps for Azure SQL Managed Instance errors, see [Known issues with Azure SQL Managed Instance](/azure/azure-sql/managed-instance/doc-changes-updates-known-issues)
+- **Cause**: The source database is a contained database. A specific configuration is needed to enable restoring a contained database. For more information about contained databases, see [Contained Database Users](/sql/relational-databases/security/contained-database-users-making-your-database-portable).
+
+- **Recommendation**: Run the following query connected to the source SQL Server in the context of the specific database before starting the migration. Then, attempt the migration of the contained database again.
+```sql  
+-- Enable "contained database authentication"
+EXEC sp_configure 'contained', 1;
+RECONFIGURE;
+```
+
+> [!NOTE]
+> For more information on general troubleshooting steps for Azure SQL Managed Instance errors, see [Known issues with Azure SQL Managed Instance](/azure/azure-sql/managed-instance/doc-changes-updates-known-issues)
 
 ## Error code: 2012 - TestConnectionFailed
 
 - **Message**: `Failed to test connections using provided Integration Runtime. Error details: 'Remote name could not be resolved.'`
 
-- **Cause**: DMS cannot connect to Self-Hosted Integration Runtime (SHIR) due to network settings in the firewall.
+- **Cause**: Your network settings in the firewall are causing the Self-Hosted Integration Runtime to be unable to connect to the service back end.
 
 - **Recommendation**: There's a Domain Name System (DNS) issue. Contact your network team to fix the issue. For more information, see [Troubleshoot Self-Hosted Integration Runtime](../data-factory/self-hosted-integration-runtime-troubleshoot-guide.md).
 
@@ -175,14 +186,15 @@ Known issues and troubleshooting steps associated with the Azure SQL Migration e
 
 - **Recommendation**: If desired, the target database can be returned to its original state by running the first query and all of the returned queries, then running the second query and doing the same. 
 
-```
+```sql  
 SELECT [ROLLBACK] FROM [dbo].[__migration_status] 
 WHERE STEP in (3,4,6);
 
 SELECT [ROLLBACK] FROM [dbo].[__migration_status]  
 WHERE STEP in (5,7,8) ORDER BY STEP DESC;
 ```
   
+
 ## Error code: 2042 - PreCopyStepsCompletedDuringCancel 
 
 - **Message**: `Pre Copy steps finished successfully before canceling completed. Target database Foreign keys and temporal tables have been altered. Schema migration may be required again for future migrations. Target server: <Target Server>, Target database: <Target Database>.`
@@ -191,7 +203,7 @@ WHERE STEP in (5,7,8) ORDER BY STEP DESC;
 
 - **Recommendation**: If desired, target database can be returned to its original state by running the following query and all of the returned queries. 
 
-```
+```sql  
 SELECT [ROLLBACK] FROM [dbo].[__migration_status]  
 WHERE STEP in (3,4,6);
 ```
@@ -204,7 +216,6 @@ WHERE STEP in (3,4,6);
 
 - **Recommendation**: For more troubleshooting steps, see [Troubleshoot Azure Data Factory and Synapse pipelines](../data-factory/data-factory-troubleshoot-guide.md#error-code-2108). 
 
-
 ## Error code: 2056 - SqlInfoValidationFailed
 
 - **Message**: CollationMismatch: `Source database collation <CollationOptionSource> is not the same as the target database <CollationOptionTarget>. Source database: <SourceDatabaseName> Target database: <TargetDatabaseName>.`
@@ -246,29 +257,34 @@ WHERE STEP in (3,4,6);
 
 - **Recommendation**: Check if the selected tables exist in the target Azure SQL Database. If this migration is called from a PowerShell script, check if the table list parameter includes the correct table names and is passed into the migration.
 
-
 ## Error code: Ext_RestoreSettingsError
 
-- **Message**: Unable to read blobs in storage container, exception: The remote server returned an error: (403) Forbidden. The remote server returned an error: (403) Forbidden
+- **Message**: Unable to read blobs in storage container, exception: The remote server returned an error: (403) Forbidden.;The remote server returned an error: (403) Forbidden
 
-- **Cause**: Target is unable to connect to blob storage.
+- **Cause**: The Azure SQL target is unable to connect to blob storage.
 
-- **Recommendation**: Confirm that target network settings allow access to blob storage. For example, if migrating to SQL VM, ensure that outbound connections on VM aren't being blocked.
+- **Recommendation**: Confirm that target network settings allow access to blob storage.  For example, if you're migrating to a SQL Server on Azure VM target, ensure that outbound connections on the Virtual Machine aren't being blocked.
 
 
-- **Message**: Failed to create restore job. Unable to read blobs in storage container, exception: The remote name could not be resolved.
+- **Message**: Failed to create restore job. Unable to read blobs in storage container, exception: The remote name couldn't be resolved.
 
-- **Cause**: Target is unable to connect to blob storage.
+- **Cause**: The Azure SQL target is unable to connect to blob storage.
 
-- **Recommendation**: Confirm that target network settings allow access to blob storage. For example, if migrating to SQL VM, ensure that outbound connections on VM are not being blocked.
+- **Recommendation**: Confirm that target network settings allow access to blob storage.  For example, if migrating to SQL VM, ensure that outbound connections on VM aren't being blocked.
 
 
 - **Message**: `Migration for Database <Database Name> failed with error 'Migration cannot be completed because provided backup file name <Backup File Name> should be the last restore backup file <Last Restore Backup File Name>'`.
 
-- **Cause**: Most recent backup was not specified in backup settings.
+- **Cause**: The most recent backup wasn't specified in the backup settings.
+
+- **Recommendation**: Specify the most recent backup file name in backup settings and retry the operation.
+
+
+- **Message**: `Operation failed: errorCode: Ext_RestoreSettingsError, message: RestoreId: 1111111-aaaa-bbbb-cccc-dddddddd, OperationId: 2222222-aaaa-bbbb-cccc-dddddddd, Detail: Unable to read blobs in storage container, exception: Unable to connect to the remote server;Unable to connect to the remote server;A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond 11.111.11.111:443.`
 
-- **Recommendation**: Specify most recent backup file name in backup settings and retry operation.
+- **Cause**: The error is possible to occur for both storage accounts with public network and private endpoint configuration. It's also possible that you have an on-premises DNS server that controls a hybrid network routing and DHCP. Unless you allow the Azure IP addresses configured in your DNS server, your SQL Server on Azure VM target has no chance to resolve the remote storage blob endpoint.
 
+- **Recommendation**: To debug this issue, you can try pinging your Azure Blob Storage URL from your SQL Server on Azure VM target and confirm if you have a connectivity problem. To solve this issue, you have to allow the Azure IP addresses configured in your DNS server. For more information, see [Troubleshoot Azure Private Endpoint connectivity problems](/azure/private-link/troubleshoot-private-endpoint-connectivity)
 
 ## Azure SQL Database limitations 
 
diff --git a/articles/dms/media/ads-sku-recommend/ads-sql-sku-recommend.png b/articles/dms/media/ads-sku-recommend/ads-sql-sku-recommend.png
diff --git a/articles/dms/tutorial-sql-server-azure-sql-database-offline-ads.md b/articles/dms/tutorial-sql-server-azure-sql-database-offline-ads.md
@@ -57,6 +57,12 @@ Before you begin the tutorial:
 
 - If you're using Azure Database Migration Service for the first time, make sure that the Microsoft.DataMigration [resource provider is registered in your subscription](quickstart-create-data-migration-service-portal.md#register-the-resource-provider).
 
+> [!NOTE]
+> Make sure to migrate the database schema from source to target by using the [SQL Server dacpac extension](/sql/azure-data-studio/extensions/sql-server-dacpac-extension) or the [SQL Database Projects extension](/sql/azure-data-studio/extensions/sql-database-project-extension) in Azure Data Studio before selecting the list of tables to migrate.
+>
+> If no tables exists on the Azure SQL Database target, or no tables are selected before starting the migration. The **Next** button isn't available to select to initiate the migration task.
+>
+
 ## Open the Migrate to Azure SQL wizard in Azure Data Studio
 
 To open the Migrate to Azure SQL wizard:
@@ -165,6 +171,8 @@ To open the Migrate to Azure SQL wizard:
 
 > [!NOTE]
 > If no tables are selected or if a username and password aren't entered, the **Next** button isn't available to select.
+>
+> Make sure to migrate the database schema from source to target by using the [SQL Server dacpac extension](/sql/azure-data-studio/extensions/sql-server-dacpac-extension) or the [SQL Database Projects extension](/sql/azure-data-studio/extensions/sql-database-project-extension) in Azure Data Studio before selecting the list of tables to migrate.
 
 ## Create a Database Migration Service instance
 
