Merge pull request #76641 from HJToland3/localworking

Fixes

Author: GitHubber17

articles/dms/known-issues-troubleshooting-dms.md

@@ -1,4 +1,4 @@
----
+---
 title: Article about known troubleshooting common issues/errors associated with using Azure Database Migration Service | Microsoft Docs
 description: Learn about how to troubleshoot common known issues/errors associated with using Azure Database Migration Service.
 services: database-migration
@@ -10,7 +10,7 @@ ms.service: dms
 ms.workload: data-services
 ms.custom: mvc
 ms.topic: article
-ms.date: 05/09/2019
+ms.date: 05/14/2019
 ---
 
 # Troubleshoot common Azure Database Migration Service issues and errors
@@ -19,7 +19,7 @@ This article describes some common issues and errors that Azure Database Migrati
 
 ## Migration activity in queued state
 
-When you create new activities on Azure Database Migration Service project, the activities remain in queued state.
+When you create new activities in an Azure Database Migration Service project, the activities remain in a queued state.
 
 | Cause         | Resolution |
 | ------------- | ------------- |
@@ -39,13 +39,13 @@ The following error occurs when creating an activity for a database migration pr
 
 When you migrate from MySQL to Azure Database for MySQL using Azure Database Migration Service, the migration activity fails with the following error:
 
-* **Error**: Error: Database migration error - Task 'TaskID' was suspended due to [n] successive recovery failures.
+* **Error**: Database migration error - Task 'TaskID' was suspended due to [n] successive recovery failures.
 
 | Cause         | Resolution |
 | ------------- | ------------- |
-| This error may occur when the user performing the  migration is missing ReplicationAdmin role and/or privileges of REPLICATION CLIENT, REPLICATION REPLICA, and SUPER (versions earlier than MySQL 5.6.6).<br> <br><br><br> <br> <br> <br> <br> <br> <br> | Make sure the [pre-requisite privileges](https://docs.microsoft.com/azure/dms/tutorial-mysql-azure-mysql-online#prerequisites) for the user account are configured accurately on Azure MySQL instance. For example, the following steps can be followed to create a user named 'migrateuser' with required privileges:<br>1. CREATE USER migrateuser@'%' IDENTIFIED BY 'secret'; <br>2. grant all privileges on db_name.* to 'migrateuser'@'%' identified by 'secret'; // repeat this step to grant access on more databases <br>3. grant replication slave on *.* to 'migrateuser'@'%' identified by 'secret';<br>4. grant replication client on *.* to 'migrateuser'@'%' identified by 'secret';<br>5. flush privileges; |
+| This error may occur when the user performing the  migration is missing ReplicationAdmin role and/or privileges of REPLICATION CLIENT, REPLICATION REPLICA, and SUPER (versions earlier than MySQL 5.6.6).<br> <br><br><br> <br> <br> <br> <br> <br> <br> | Make sure the [pre-requisite privileges](https://docs.microsoft.com/azure/dms/tutorial-mysql-azure-mysql-online#prerequisites) for the user account are configured accurately on the Azure Database for MySQL instance. For example, the following steps can be followed to create a user named 'migrateuser' with required privileges:<br>1. CREATE USER migrateuser@'%' IDENTIFIED BY 'secret'; <br>2. Grant all privileges on db_name.* to 'migrateuser'@'%' identified by 'secret'; // repeat this step to grant access on more databases <br>3. Grant replication slave on *.* to 'migrateuser'@'%' identified by 'secret';<br>4. Grant replication client on *.* to 'migrateuser'@'%' identified by 'secret';<br>5. Flush privileges; |
 
-## Error when attempting to stop the Azure Database Migration Service instance
+## Error when attempting to stop Azure Database Migration Service
 
 You receive following error when stopping the Azure Database Migration Service instance:
 
@@ -55,7 +55,7 @@ You receive following error when stopping the Azure Database Migration Service i
 | ------------- | ------------- |
 | This error displays when the service instance you're attempting to stop includes activities that are still running or present in migration projects. <br><br><br><br><br><br> | Ensure that there are no activities running in the instance of Azure Database Migration Service you're trying to stop. You may also delete the activities or projects before attempting to stop the service. The following steps illustrate how to remove projects to clean up the migration service instance by deleting all running tasks:<br>1. Install-Module -Name AzureRM.DataMigration <br>2. Login-AzureRmAccount <br>3. Select-AzureRmSubscription -SubscriptionName "<subName>" <br> 4. Remove-AzureRmDataMigrationProject -Name <projectName> -ResourceGroupName <rgName> -ServiceName <serviceName> -DeleteRunningTask |
 
-## Error restoring database while migrating from SQL Server to an Azure SQL Database managed instance
+## Error restoring database while migrating SQL to Azure SQL DB managed instance
 
 When you perform an online migration from SQL Server to an Azure SQL Database managed instance, the cutover fails with following error:
 
@@ -83,25 +83,25 @@ When you try to connect to source in the Azure Database Migration service projec
 | ------------- | ------------- |
 | When using [ExpressRoute](https://azure.microsoft.com/services/expressroute/), Azure Database Migration Service [requires](https://docs.microsoft.com/azure/dms/tutorial-sql-server-azure-sql-online) provisioning three service endpoints on the Virtual Network subnet associated with the service:<br> -- Service Bus endpoint<br> -- Storage endpoint<br> -- Target database endpoint (e.g. SQL endpoint, Cosmos DB endpoint)<br><br><br><br> | [Enable](https://docs.microsoft.com/azure/dms/tutorial-sql-server-azure-sql-online) the required service endpoints for ExpressRoute connectivity between source and Azure Database Migration Service. <br><br><br><br><br><br><br><br> |
 
-## Timeout error when migrating a MySQL database to Azure Database for MySQL
+## Timeout error when migrating a MySQL database to Azure MySQL
 
 When you migrate a MySQL database to an Azure Database for MySQL instance via Azure Database Migration Service, the migration fails with following timeout error:
 
-    * **Error**: Error: Database migration error - Failed to load file - Failed to start load process for file 'n' RetCode: SQL_ERROR SqlState: HY000 NativeError: 1205 Message: [MySQL][ODBC Driver][mysqld] Lock wait timeout exceeded; try restarting transaction
+* **Error**: Database migration error - Failed to load file - Failed to start load process for file 'n' RetCode: SQL_ERROR SqlState: HY000 NativeError: 1205 Message: [MySQL][ODBC Driver][mysqld] Lock wait timeout exceeded; try restarting transaction
 
 | Cause         | Resolution    |
 | ------------- | ------------- |
 | This error occurs when migration fails because of  the lock wait timeout during migration.<br><br> | Consider increasing the value of server parameter **'innodb_lock_wait_timeout'**. The highest allowed value is 1073741824. |
 
 ## Additional known issues
 
-* [Known issues/migration limitations with online migrations to Azure SQL DB](https://docs.microsoft.com/azure/dms/known-issues-azure-sql-online)
-* [Known issues/migration limitations with online migrations to Azure DB for MySQL](https://docs.microsoft.com/azure/dms/known-issues-azure-mysql-online)
-* [Known issues/migration limitations with online migrations to Azure DB for PostgreSQL](https://docs.microsoft.com/azure/dms/known-issues-azure-postgresql-online)
+* [Known issues/migration limitations with online migrations to Azure SQL Database](https://docs.microsoft.com/azure/dms/known-issues-azure-sql-online)
+* [Known issues/migration limitations with online migrations to Azure Database for MySQL](https://docs.microsoft.com/azure/dms/known-issues-azure-mysql-online)
+* [Known issues/migration limitations with online migrations to Azure Database for PostgreSQL](https://docs.microsoft.com/azure/dms/known-issues-azure-postgresql-online)
 
-## Additional resources
+## Next steps
 
-* [Azure Database Migration Service PowerShell](https://docs.microsoft.com/powershell/module/azurerm.datamigration/?view=azurermps-6.13.0#data_migration)
-* [How to configure server parameters in Azure Database for MySQL by using the Azure portal](https://docs.microsoft.com/azure/mysql/howto-server-parameters)
-* [Overview of prerequisites for using Azure Database Migration Service](https://docs.microsoft.com/azure/dms/pre-reqs)
-* [FAQ about using Azure Database Migration Service](https://docs.microsoft.com/azure/dms/faq)
+* View the article [Azure Database Migration Service PowerShell](https://docs.microsoft.com/powershell/module/azurerm.datamigration/?view=azurermps-6.13.0#data_migration).
+* View the article [How to configure server parameters in Azure Database for MySQL by using the Azure portal](https://docs.microsoft.com/azure/mysql/howto-server-parameters).
+* View the article [Overview of prerequisites for using Azure Database Migration Service](https://docs.microsoft.com/azure/dms/pre-reqs).
+* See the [FAQ about using Azure Database Migration Service](https://docs.microsoft.com/azure/dms/faq).

articles/dms/tutorial-sql-server-to-azure-sql.md

@@ -10,7 +10,7 @@ ms.service: dms
 ms.workload: data-services
 ms.custom: mvc, tutorial
 ms.topic: article
-ms.date: 05/08/2019
+ms.date: 05/14/2019
 ---
 
 # Tutorial: Migrate SQL Server to a single database or pooled database in Azure SQL Database offline using DMS
@@ -19,6 +19,7 @@ You can use the Azure Database Migration Service to migrate the databases from a
 
 In this tutorial, you learn how to:
 > [!div class="checklist"]
+>
 > - Assess your on-premises database by using the Data Migration Assistant.
 > - Migrate the sample schema by using the Data Migration Assistant.
 > - Create an instance of the Azure Database Migration Service.
@@ -58,7 +59,7 @@ To complete this tutorial, you need to:
 - Open your Windows firewall to allow the Azure Database Migration Service to access the source SQL Server, which by default is TCP port 1433.
 - If you're running multiple named SQL Server instances using dynamic ports, you may wish to enable the SQL Browser Service and allow access to UDP port 1434 through your firewalls so that the Azure Database Migration Service can connect to a named instance on your source server.
 - When using a firewall appliance in front of your source database(s), you may need to add firewall rules to allow the Azure Database Migration Service to access the source database(s) for migration.
-- Create a server-level IP [firewall rule](https://docs.microsoft.com/azure/sql-database/sql-database-firewall-configure) for the Azure SQL Database server to allow the Azure Database Migration Service access to the target databases. Provide the subnet range of the VNET used for the Azure Database Migration Service.
+- Create a server-level IP [firewall rule](https://docs.microsoft.com/azure/sql-database/sql-database-firewall-configure) for the Azure SQL Database server to allow the Azure Database Migration Service access to the target databases. Provide the subnet range of the VNet used for the Azure Database Migration Service.
 - Ensure that the credentials used to connect to source SQL Server instance have [CONTROL SERVER](https://docs.microsoft.com/sql/t-sql/statements/grant-server-permissions-transact-sql) permissions.
 - Ensure that the credentials used to connect to target Azure SQL Database instance have CONTROL DATABASE permission on the target Azure SQL databases.
 
@@ -74,7 +75,7 @@ Before you can migrate data from an on-premises SQL Server instance to a single
    - Check database compatibility
    - Check feature parity
 
-     Both report types are selected by default.
+    Both report types are selected by default.
 
 3. In the Data Migration Assistant, on the **Options** screen, select **Next**.
 4. On the **Select sources** screen, in the **Connect to a server** dialog box, provide the connection details to your SQL Server, and then select **Connect**.