Merge pull request #234802 from sandeepsnairms/DMA-ADS

PMEds28 · web-flow · commit 3ff1946d7a36 · 2023-04-20T15:52:56.000+01:00
ADS- DMA
diff --git a/articles/cosmos-db/mongodb/TOC.yml b/articles/cosmos-db/mongodb/TOC.yml
@@ -415,6 +415,8 @@
                   href: ../free-tier.md
                 - name: Premigration guide
                   href: pre-migration-steps.md
+                - name: Programmatic Database Migration Assistant (legacy)
+                  href: programmatic-database-migration-assistant-legacy.md
                 - name: MongoDB native tools (offline)
                   href: tutorial-mongotools-cosmos-db.md
                 - name: Database Migration Service (online)
diff --git a/articles/cosmos-db/mongodb/pre-migration-steps.md b/articles/cosmos-db/mongodb/pre-migration-steps.md
@@ -8,10 +8,10 @@ ms.service: cosmos-db
 ms.subservice: mongodb
 ms.custom: ignite-2022
 ms.topic: conceptual
-ms.date: 02/27/2023
+ms.date: 04/20/2023
 ---
 
-# Pre-migration steps for data migrations from MongoDB to Azure Cosmos DB for MongoDB
+# Premigration steps for data migrations from MongoDB to Azure Cosmos DB for MongoDB
 
 [!INCLUDE[MongoDB](../includes/appliesto-mongodb.md)]
 
@@ -34,10 +34,9 @@ Your goal in pre-migration is to:
 
 Follow these steps to perform a thorough pre-migration
 
-1. [Discover your existing MongoDB resources and create a data estate spreadsheet to track them](#pre-migration-discovery)
-2. [Assess the readiness of your existing MongoDB resources for data migration](#pre-migration-assessment)
-3. [Map your existing MongoDB resources to new Azure Cosmos DB resources](#pre-migration-mapping)
-4. [Plan the logistics of migration process end-to-end, before you kick off the full-scale data migration](#execution-logistics)
+1. [Discover your existing MongoDB resources and Assess the readiness of your existing MongoDB resources for data migration](#pre-migration-assessment)
+2. [Map your existing MongoDB resources to new Azure Cosmos DB resources](#pre-migration-mapping)
+3. [Plan the logistics of migration process end-to-end, before you kick off the full-scale data migration](#execution-logistics)
 
 Then, execute your migration in accordance with your pre-migration plan.
 
@@ -47,47 +46,29 @@ All of the above steps are critical for ensuring a successful migration.
 
 When you plan a migration, we recommend that whenever possible you plan at the per-resource level.
 
-The [Database Migration Assistant](https://github.com/AzureCosmosDB/Cosmos-DB-Migration-Assistant-for-API-for-MongoDB)(DMA) assists you with the [Discovery](#programmatic-discovery-using-the-database-migration-assistant) and [Assessment](#programmatic-assessment-using-the-database-migration-assistant) stages of the planning.
-
-## Pre-migration discovery
-
-The first pre-migration step is resource discovery. In this step, you need to create a **data estate migration spreadsheet**.
+## Pre-migration assessment
 
-* This sheet contains a comprehensive list of the existing resources (databases or collections) in your MongoDB data estate.
-* The purpose of this spreadsheet is to enhance your productivity and help you to plan migration from end-to-end.
-* You're recommended to extend this document and use it as a tracking document throughout the migration process.
+The first pre-migration step is to discover your existing MongoDB resources and assess the readiness of your resources for migration.
 
-### Programmatic discovery using the Database Migration Assistant
+Discovery involves creating a comprehensive list of the existing resources (databases or collections) in your MongoDB data estate.
 
-You may use the [Database Migration Assistant](https://github.com/AzureCosmosDB/Cosmos-DB-Migration-Assistant-for-API-for-MongoDB) (DMA) to assist you with the discovery stage and create the data estate migration sheet programmatically.
+Assessment involves finding out whether you're using the [features and syntax that are supported](./feature-support-42.md). It also includes making sure you're adhering to the [limits and quotas](../concepts-limits.md#per-account-limits). The aim of this stage is to create a list of incompatibilities and warnings, if any. After you have the assessment results, you can try to address the findings during rest of the migration planning.
 
-It's easy to [setup and run DMA](https://github.com/AzureCosmosDB/Cosmos-DB-Migration-Assistant-for-API-for-MongoDB#how-to-run-the-dma) through an Azure Data Studio client. It can be run from any machine connected to your source MongoDB environment.
+There are 3 ways to complete the pre-migration assessment, we recommend you to use the [Azure Cosmos DB Migration for MongoDB extension](#azure-cosmos-db-migration-for-mongodb-extension).
 
-You can use either one of the following DMA output files as the data estate migration spreadsheet:
+### Azure Cosmos DB Migration for MongoDB extension
 
-* `workload_database_details.csv` - Gives a database-level view of the source workload. Columns in file are: Database Name, Collection count, Document Count, Average Document Size, Data Size, Index Count and Index Size.
-* `workload_collection_details.csv` - Gives a collection-level view of the source workload. Columns in file are: Database Name, Collection Name, Doc Count, Average Document Size, Data size, Index Count, Index Size and Index definitions.
+The [Azure Cosmos DB Migration for MongoDB extension](/sql/azure-data-studio/extensions/database-migration-for-mongo-extension) in Azure Data Studio helps you assess a MongoDB workload for migrating to Azure Cosmos DB for MongoDB. You can use this extension to run an end-to-end assessment on your workload and find out the actions that you may need to take to seamlessly migrate your workloads on Azure Cosmos DB. During  the assessment of a MongoDB endpoint, the extension reports all the discovered resources.
 
-Here's a sample database-level migration spreadsheet created by DMA:
 
-| DB Name | Collection Count | Doc Count | Avg Doc Size | Data Size | Index Count | Index Size |
-| --- | --- | --- | --- | --- | --- | --- |
-| `bookstoretest` | 2 | 192200 | 4144 | 796572532 | 7 | 260636672 |
-| `cosmosbookstore` | 1 | 96604 | 4145 | 400497620 | 1 | 1814528 |
-| `geo` | 2 | 25554 | 252 | 6446542 | 2 | 266240 |
-| `kagglemeta` | 2 | 87934912 | 190 | 16725184704 | 2 | 891363328 |
-| `pe_orig` | 2 | 57703820 | 668 | 38561434711 | 2 | 861605888 |
-| `portugeseelection` | 2 | 30230038 | 687 | 20782985862 | 1 | 450932736 |
-| `sample_mflix` | 5 | 75583 | 691 | 52300763 | 5 | 798720 |
-| `test` | 1 | 22 | 545 | 12003 | 0 | 0 |
-| `testcol` | 26 | 46 | 88 | 4082 | 32 | 589824 |
-| `testhav` | 3 | 2 | 528 | 1057 | 3 | 36864 |
-| **TOTAL:** | **46** | **176258781** | | **72.01 GB** | | **2.3 GB** |
+> [!NOTE]
+> Azure Cosmos DB Migration for MongoDB extension does not perform an end-to-end assessment. We recommend you to go through [the supported features and syntax](./feature-support-42.md), [Azure Cosmos DB limits and quotas](../concepts-limits.md#per-account-limits) in detail, as well as perform a proof-of-concept prior to the actual migration.
 
-### Manual discovery
+### Manual discovery (legacy) 
 
-Alternately, you may refer to the sample spreadsheet in this guide and create a similar document yourself.
+Alternatively, you could create a **data estate migration spreadsheet**. The purpose of this spreadsheet is to enhance your productivity and help you to plan migration from end-to-end and use it as a tracking document throughout the migration process.
 
+* This sheet contains a comprehensive list of the existing resources (databases or collections) in your MongoDB data estate.
 * The spreadsheet should be structured as a record of your data estate resources, in list form.
 * Each row corresponds to a resource (database or collection).
 * Each column corresponds to a property of the resource; start with at least *name* and *data size (GB)* as columns.
@@ -98,25 +79,14 @@ Here are some tools you can use for discovering resources:
 * [MongoDB Shell](https://www.mongodb.com/try/download/shell)
 * [MongoDB Compass](https://www.mongodb.com/try/download/compass)
 
-## Pre-migration assessment
-
-Second, as a prelude to planning your migration, assess the readiness of resources in your data estate for migration.
-
-Assessment involves finding out whether you're using the [features and syntax that are supported](./feature-support-42.md). It also includes making sure you're adhering to the [limits and quotas](../concepts-limits.md#per-account-limits). The aim of this stage is to create a list of incompatibilities and warnings, if any. After you have the assessment results, you can try to address the findings during rest of the migration planning.
-
-### Programmatic assessment using the Database Migration Assistant
+Go through the spreadsheet and verify each collection against the [supported features and syntax](./feature-support-42.md), and [Azure Cosmos DB limits and quotas](../concepts-limits.md#per-account-limits) in detail.
 
-[Database Migration Assistant](https://github.com/AzureCosmosDB/Cosmos-DB-Migration-Assistant-for-API-for-MongoDB) (DMA) also assists you with the assessment stage of pre-migration planning.
-
-Refer to the section [Programmatic discovery using the Database Migration Assistant](#programmatic-discovery-using-the-database-migration-assistant) to know how to setup and run DMA.
-
-The DMA notebook runs a few assessment rules against the resource list it gathers from source MongoDB. The assessment result lists the required and recommended changes needed to proceed with the migration.
-
-The results are printed as an output in the DMA notebook and saved to a CSV file - `assessment_result.csv`.
+### Database Migration Assistant utility (legacy) 
 
 > [!NOTE]
-> Database Migration Assistant is a preliminary utility meant to assist you with the pre-migration steps. It does not perform an end-to-end assessment.
-> In addition to running the DMA, we also recommend you to go through [the supported features and syntax](./feature-support-42.md), [Azure Cosmos DB limits and quotas](../concepts-limits.md#per-account-limits) in detail, as well as perform a proof-of-concept prior to the actual migration.
+> Database Migration Assistant is a legacy utility meant to assist you with the pre-migration steps. We recommend you to use the [Azure Cosmos DB Migration for MongoDB extension](#azure-cosmos-db-migration-for-mongodb-extension) for all pre-migration steps.
+
+You may use the [Database Migration Assistant](programmatic-database-migration-assistant-legacy.md) (DMA) utility to assist you with pre-migration steps.
 
 ## Pre-migration mapping
 
diff --git a/articles/cosmos-db/mongodb/programmatic-database-migration-assistant-legacy.md b/articles/cosmos-db/mongodb/programmatic-database-migration-assistant-legacy.md
@@ -0,0 +1,60 @@
+---
+title: Database Migration Assistant utility
+titleSuffix: Azure Cosmos DB for MongoDB
+description: This doc provides an overview of the Database Migration Assistant legacy utility.
+author: sandeep-nair
+ms.author: sandnair
+ms.service: cosmos-db
+ms.subservice: mongodb
+ms.custom: 
+ms.topic: conceptual
+ms.date: 04/20/2023
+---
+
+# Database Migration Assistant utility (legacy)
+
+[!INCLUDE[MongoDB](../includes/appliesto-mongodb.md)]
+
+> [!IMPORTANT]  
+> Database Migration Assistant is a preliminary legacy utility meant to assist you with the pre-migration steps. Microsoft recommends you to use the [Azure Cosmos DB Migration for MongoDB extension](/sql/azure-data-studio/extensions/database-migration-for-mongo-extension) for all pre-migration steps.
+
+### Programmatic discovery using the Database Migration Assistant
+
+You may use the [Database Migration Assistant](https://github.com/AzureCosmosDB/Cosmos-DB-Migration-Assistant-for-API-for-MongoDB) (DMA) to assist you with the discovery stage and create the data estate migration sheet programmatically.
+
+It's easy to [setup and run DMA](https://github.com/AzureCosmosDB/Cosmos-DB-Migration-Assistant-for-API-for-MongoDB#how-to-run-the-dma) through an Azure Data Studio client. It can be run from any machine connected to your source MongoDB environment.
+
+You can use either one of the following DMA output files as the data estate migration spreadsheet:
+
+* `workload_database_details.csv` - Gives a database-level view of the source workload. Columns in file are: Database Name, Collection count, Document Count, Average Document Size, Data Size, Index Count and Index Size.
+* `workload_collection_details.csv` - Gives a collection-level view of the source workload. Columns in file are: Database Name, Collection Name, Doc Count, Average Document Size, Data size, Index Count, Index Size and Index definitions.
+
+Here's a sample database-level migration spreadsheet created by DMA:
+
+| DB Name | Collection Count | Doc Count | Avg Doc Size | Data Size | Index Count | Index Size |
+| --- | --- | --- | --- | --- | --- | --- |
+| `bookstoretest` | 2 | 192200 | 4144 | 796572532 | 7 | 260636672 |
+| `cosmosbookstore` | 1 | 96604 | 4145 | 400497620 | 1 | 1814528 |
+| `geo` | 2 | 25554 | 252 | 6446542 | 2 | 266240 |
+| `kagglemeta` | 2 | 87934912 | 190 | 16725184704 | 2 | 891363328 |
+| `pe_orig` | 2 | 57703820 | 668 | 38561434711 | 2 | 861605888 |
+| `portugeseelection` | 2 | 30230038 | 687 | 20782985862 | 1 | 450932736 |
+| `sample_mflix` | 5 | 75583 | 691 | 52300763 | 5 | 798720 |
+| `test` | 1 | 22 | 545 | 12003 | 0 | 0 |
+| `testcol` | 26 | 46 | 88 | 4082 | 32 | 589824 |
+| `testhav` | 3 | 2 | 528 | 1057 | 3 | 36864 |
+| **TOTAL:** | **46** | **176258781** | | **72.01 GB** | | **2.3 GB** |
+
+### Programmatic assessment using the Database Migration Assistant
+
+[Database Migration Assistant](https://github.com/AzureCosmosDB/Cosmos-DB-Migration-Assistant-for-API-for-MongoDB) (DMA) also assists you with the assessment stage of pre-migration planning.
+
+Refer to the section [Programmatic discovery using the Database Migration Assistant](#programmatic-discovery-using-the-database-migration-assistant) to know how to setup and run DMA.
+
+The DMA notebook runs a few assessment rules against the resource list it gathers from source MongoDB. The assessment result lists the required and recommended changes needed to proceed with the migration.
+
+The results are printed as an output in the DMA notebook and saved to a CSV file - `assessment_result.csv`.
+
+> [!NOTE]
+> Database Migration Assistant does not perform an end-to-end assessment. It is a preliminary utility meant to assist you with the pre-migration steps.
+
