Merge pull request #50041 from HJToland3/master

ktoliver · web-flow · commit c518ae29cd0c · 2018-08-27T08:40:47.000-07:00
tweaks to new articles
diff --git a/articles/dms/TOC.md b/articles/dms/TOC.md
@@ -7,8 +7,8 @@
 # Tutorials
 ## [Migrate SQL Server to Azure SQL DB offline](tutorial-sql-server-to-azure-sql.md)
 ## [Migrate SQL Server to Azure SQL DB online](tutorial-sql-server-azure-sql-online.md)
-## [Migrate SQL Server to Azure SQL DB Managed Instance](tutorial-sql-server-to-managed-instance.md)
-## [Migrate MySQL to Azure DB for MySQL](tutorial-mysql-azure-mysql-online.md)
+## [Migrate SQL Server to Azure SQL DB Managed Instance offline](tutorial-sql-server-to-managed-instance.md)
+## [Migrate MySQL to Azure DB for MySQL online](tutorial-mysql-azure-mysql-online.md)
 
 # How-to guides
 ## [Use PowerShell to migrate SQL Server to Azure SQL DB](howto-sql-server-to-azure-sql-powershell.md)
diff --git a/articles/dms/dms-overview.md b/articles/dms/dms-overview.md
@@ -9,7 +9,7 @@ ms.reviewer: douglasl
 ms.service: database-migration
 ms.workload: data-services
 ms.topic: article
-ms.date: 08/20/2018
+ms.date: 08/27/2018
 ---
 # What is the Azure Database Migration Service?
 The Azure Database Migration Service is a fully managed service designed to enable seamless migrations from multiple database sources to Azure Data platforms with minimal downtime.
@@ -20,6 +20,12 @@ The Azure Database Migration Service integrates some of the functionality of our
 ## Regional availability
 For up-to-date information about the regions in which the Database Migration Service is available, see [Products available by region](https://azure.microsoft.com/global-infrastructure/services/).
 
+> [!NOTE]
+> Online migrations and SKU recommendation functionality are currently available only in the following regions:
+> - Cental US
+> - East US2
+> - West Europe
+
 ## Next steps
 - [Create an instance of the Azure Database Migration Service by using the Azure portal](quickstart-create-data-migration-service-portal.md).
 - [Migrate SQL Server to Azure SQL Database](tutorial-sql-server-to-azure-sql.md).
diff --git a/articles/dms/how-to-monitor-migration-activity.md b/articles/dms/how-to-monitor-migration-activity.md
@@ -10,13 +10,13 @@ ms.service: database-migration
 ms.workload: data-services
 ms.custom: mvc
 ms.topic: article
-ms.date: 08/24/2018
+ms.date: 08/27/2018
 ---
 
-# Monitoring migration activity
+# Monitor migration activity
 In this article, you learn how to monitor the progress of a migration at both a database level and a table level.
 
-## Monitoring activity at the database level
+## Monitor at the database level
 To monitor activity at the database level, view the database-level blade:
 
 ![Database-level blade](media\how-to-monitor-migration-activity\dms-database-level-blade.png)
@@ -36,7 +36,7 @@ The following table lists the fields on the database-level blade and describes t
   </thead>
   <tbody>
     <tr>
-      <td rowspan="3" class="ActivityStatus">Activity status</td>
+      <td rowspan="3" class="ActivityStatus"><strong>Activity status</strong></td>
       <td>Running</td>
       <td>Migration activity is running.</td>
     </tr>
@@ -49,7 +49,7 @@ The following table lists the fields on the database-level blade and describes t
       <td>Migration failed. Select the ‘See error details’ link under migration details for the complete error message.</td>
     </tr>
     <tr>
-      <td rowspan="4" class="Status">Status</td>
+      <td rowspan="4" class="Status"><strong>Status</strong></td>
       <td>Initializing</td>
       <td>DMS is setting up the migration pipeline.</td>
     </tr>
@@ -66,7 +66,7 @@ The following table lists the fields on the database-level blade and describes t
       <td>Migration failed. Click on migration details to see migration errors.</td>
     </tr>
     <tr>
-      <td rowspan="5" class="migration-details">Migration Details</td>
+      <td rowspan="5" class="migration-details"><strong>Migration details</strong></td>
       <td>Initiating the migration pipeline</td>
       <td>DMS is setting up the migration pipeline.</td>
     </tr>
@@ -87,14 +87,14 @@ The following table lists the fields on the database-level blade and describes t
       <td>Click on the link to show error details.</td>
     </tr>
     <tr>
-      <td rowspan="1" class="duration">Duration</td>
+      <td rowspan="1" class="duration"><strong>Duration</strong></td>
       <td>N/A</td>
       <td>Total time from migration activity being initialized to migration completed or migration faulted.</td>
     </tr>
      </tbody>
 </table>
 
-## Monitoring migration activity at table level – Quick Summary
+## Monitor at table level – Quick Summary
 To monitor activity at the table level, view the table-level blade. The top portion of the blade shows the detailed number of rows migrated in full load and incremental updates. 
 
 The bottom portion of the blade lists the tables and shows a quick summary of migration progress.
@@ -105,17 +105,17 @@ The following table describes the fields shown in the table-level details.
 
 | Field name        | Description       |
 | ------------- | ------------- |
-| Full load completed      | Number of tables completed full data load. |
-| Full load queued      | Number of tables being queued for full load.      |
-| Full load loading | Number of tables failed.      |
-| Incremental updates      | Number of change data capture (CDC) updates in rows applied to target. |
-| Incremental inserts      | Number of CDC inserts in rows applied to target.      |
-| Incremental deletes | Number of CDC deletes in rows applied to target.      |
-| Pending changes      | Number of CDC in rows that are still waiting to get applied to target. |
-| Applied changes      | Total of CDC updates, inserts, and deletes in rows applied to target.      |
-| Tables in error state | Number of tables that are in ‘error’ state during migration. Some examples that tables can go into error state are when there are duplicates identified in the target or data isn't compatible loading in the target table.      |
-
-## Monitoring migration activity at table level – Detailed Summary
+| **Full load completed**      | Number of tables completed full data load. |
+| **Full load queued**      | Number of tables being queued for full load.      |
+| **Full load loading** | Number of tables failed.      |
+| **Incremental updates**      | Number of change data capture (CDC) updates in rows applied to target. |
+| **Incremental inserts**      | Number of CDC inserts in rows applied to target.      |
+| **Incremental deletes** | Number of CDC deletes in rows applied to target.      |
+| **Pending changes**      | Number of CDC in rows that are still waiting to get applied to target. |
+| **Applied changes**      | Total of CDC updates, inserts, and deletes in rows applied to target.      |
+| **Tables in error state** | Number of tables that are in ‘error’ state during migration. Some examples that tables can go into error state are when there are duplicates identified in the target or data isn't compatible loading in the target table.      |
+
+## Monitor at table level – Detailed Summary
 There are two tabs that show migration progress in Full load and Incremental data sync.
 	
 ![Full load tab](media\how-to-monitor-migration-activity\dms-full-load-tab.png)
@@ -126,12 +126,12 @@ The following table describes the fields shown in table level migration progress
 
 | Field name        | Description       |
 | ------------- | ------------- |
-| Status - Syncing      | Continuous sync is running. |
-| Insert      | Number of CDC inserts in rows applied to target.      |
-| Update | Number of CDC updates in rows applied to target.      |
-| Delete      | Number of CDC deletes in rows applied to target. |
-| Total Applied      | Total of CDC updates, inserts, and deletes in rows applied to target. |
-| Data Errors | Number of data errors happened in this table. Some examples of the errors are *511: Cannot create a row of size %d which is greater than the allowable maximum row size of %d, 8114: Error converting data type %ls to %ls.*  Customer should query from attms_apply_exceptions table in Azure target to see the error details.    |
+| **Status - Syncing**      | Continuous sync is running. |
+| **Insert**      | Number of CDC inserts in rows applied to target.      |
+| **Update** | Number of CDC updates in rows applied to target.      |
+| **Delete**      | Number of CDC deletes in rows applied to target. |
+| **Total Applied**      | Total of CDC updates, inserts, and deletes in rows applied to target. |
+| **Data Errors** | Number of data errors happened in this table. Some examples of the errors are *511: Cannot create a row of size %d which is greater than the allowable maximum row size of %d, 8114: Error converting data type %ls to %ls.*  Customer should query from attms_apply_exceptions table in Azure target to see the error details.    |
 
 > [!NOTE]
 > CDC values of Insert, Update and Delete and Total Applied may decrease when database is cutover or migration is restarted.
diff --git a/articles/dms/tutorial-mysql-azure-mysql-online.md b/articles/dms/tutorial-mysql-azure-mysql-online.md
@@ -10,7 +10,7 @@ ms.service: dms
 ms.workload: data-services
 ms.custom: mvc, tutorial
 ms.topic: article
-ms.date: 08/24/2018
+ms.date: 08/27/2018
 ---
 
 # Migrate MySQL to Azure Database for MySQL online using DMS
@@ -209,5 +209,6 @@ After the initial Full load is completed, the databases are marked **Ready to cu
 4. When the database migration status shows **Completed**, connect your applications to the new target Azure SQL Database.
  
 ## Next steps
--	For information about the Azure Database Migration Service, see the article [What is the Azure Database Migration Service?](https://docs.microsoft.com/azure/dms/dms-overview).
--	For information about the Azure Database for MySQL, see the article [What is the Azure Database for MySQL?](https://docs.microsoft.com/azure/mysql/overview).
+- For information about known issues and limitations when performing online migrations to Azure Database for MySQL, see the article [Known issues and workarounds with Azure Database for MySQL online migrations](known-issues-azure-mysql-online.md).
+- For information about the Azure Database Migration Service, see the article [What is the Azure Database Migration Service?](https://docs.microsoft.com/azure/dms/dms-overview).
+- For information about the Azure Database for MySQL, see the article [What is the Azure Database for MySQL?](https://docs.microsoft.com/azure/mysql/overview).
diff --git a/articles/dms/tutorial-sql-server-azure-sql-online.md b/articles/dms/tutorial-sql-server-azure-sql-online.md
@@ -10,7 +10,7 @@ ms.service: dms
 ms.workload: data-services
 ms.custom: mvc, tutorial
 ms.topic: article
-ms.date: 08/24/2018
+ms.date: 08/27/2018
 ---
 
 # Migrate SQL Server to Azure SQL Database online using DMS
@@ -284,5 +284,6 @@ After the initial Full load is completed, the databases are marked **Ready to cu
     ![Activity Status - completed](media\tutorial-sql-server-to-azure-sql-online\dms-activity-completed.png)
 
 ## Next steps
--	For information about the Azure Database Migration Service, see the article [What is the Azure Database Migration Service?](https://docs.microsoft.com/azure/dms/dms-overview).
--	For information about the Azure SQL Database, see the article [What is the Azure SQL Database service?](https://docs.microsoft.com/azure/sql-database/sql-database-technical-overview).
+- For information about known issues and limitations when performing online migrations to Azure Database for MySQL, see the article [Known issues and workarounds with Azure SQL Database online migrations](known-issues-azure-sql-online.md).
+- For information about the Azure Database Migration Service, see the article [What is the Azure Database Migration Service?](https://docs.microsoft.com/azure/dms/dms-overview).
+- For information about the Azure SQL Database, see the article [What is the Azure SQL Database service?](https://docs.microsoft.com/azure/sql-database/sql-database-technical-overview).
