Merge pull request #219136 from seesharprun/cosmos-retire-migration-tool

Cosmos DB | Retire data migration tool mentions (1/2)

Author: prmerger-automator[bot]

articles/cosmos-db/configure-periodic-backup-restore.md

@@ -227,7 +227,6 @@ After you restore the data, you get a notification about the name of the new acc
 
 The following are different ways to migrate data back to the original account:
 
-* Use the [Azure Cosmos DB data migration tool](import-data.md).
 * Use the [Azure Data Factory](../data-factory/connector-azure-cosmos-db.md).
 * Use the [change feed](change-feed.md) in Azure Cosmos DB.
 * You can write your own custom code.

articles/cosmos-db/faq.yml

@@ -218,7 +218,6 @@ sections:
           You can bulk-insert documents into Azure Cosmos DB in one of the following ways:
           
           * The bulk executor tool, as described in [Using bulk executor .NET library](nosql/bulk-executor-dotnet.md) and [Using bulk executor Java library](bulk-executor-java.md)
-          * The data migration tool, as described in [Database migration tool for Azure Cosmos DB](import-data.md).
           * Stored procedures, as described in [Server-side JavaScript programming for Azure Cosmos DB](stored-procedures-triggers-udfs.md).
           
       - question: |

articles/cosmos-db/index.yml

@@ -136,13 +136,11 @@ additionalContent:
       items:
       - title: Migration options
         links:
-          - text: Data migration tool – API for NoSQL
-            url: import-data.md
           - text: CQL shell, Spark – API for Cassandra
             url: cassandra/migrate-data.md
           - text: Azure Database Migration Service – API for MongoDB
             url: ../dms/tutorial-mongodb-cosmos-db.md
-          - text: AzCopy, Data migration tool – API for Table
+          - text: AzCopy – API for Table
             url: table/import.md                         
       - title: Migration guides
         links:

articles/cosmos-db/local-emulator.md

@@ -28,8 +28,6 @@ The Azure Cosmos DB Emulator provides a high-fidelity emulation of the Azure Cos
 
 While emulation of the Azure Cosmos DB service is faithful, the emulator's implementation is different than the service. For example, the emulator uses standard OS components such as the local file system for persistence, and the HTTPS protocol stack for connectivity. Functionality that relies on the Azure infrastructure like global replication, single-digit millisecond latency for reads/writes, and tunable consistency levels are not applicable when you use the emulator.
 
-You can migrate data between the Azure Cosmos DB Emulator and the Azure Cosmos DB service by using the [Azure Cosmos DB Data Migration Tool](https://github.com/azure/azure-documentdb-datamigrationtool).
-
 ## Differences between the emulator and the cloud service
 
 Because the Azure Cosmos DB Emulator provides an emulated environment that runs on the local developer workstation, there are some differences in functionality between the emulator and an Azure Cosmos DB account in the cloud:

articles/cosmos-db/merge.md

@@ -169,7 +169,6 @@ To enroll in the preview, your Azure Cosmos DB account must meet all the followi
   - Azure Functions
   - Azure Search
   - Azure Cosmos DB Spark connector
-  - Azure Cosmos DB data migration tool
   - Any third party library or tool that has a dependency on an Azure Cosmos DB SDK that isn't .NET V3 SDK v3.27.0 or higher
 
 ### Account resources and configuration
@@ -209,7 +208,6 @@ If you enroll in the preview, the following connectors will fail.
 - Azure Functions <sup>1</sup>
 - Azure Search <sup>1</sup>
 - Azure Cosmos DB Spark connector <sup>1</sup>
-- Azure Cosmos DB data migration tool
 - Any third party library or tool that has a dependency on an Azure Cosmos DB SDK that isn't .NET V3 SDK v3.27.0 or higher
 
 <sup>1</sup> Support for these connectors is planned for the future.

articles/cosmos-db/migrate.md

@@ -20,7 +20,7 @@ Before you migrate the entire workload to Azure Cosmos DB, you can migrate a sub
 
 ## Tools for data migration 
 
-Azure Cosmos DB migration strategies currently differ based on the API choice and the size of the data. To migrate smaller datasets – for validating data modeling, query performance, partition key choice etc. – you can choose the [Data Migration Tool](import-data.md) or [Azure Data Factory’s Azure Cosmos DB connector](../data-factory/connector-azure-cosmos-db.md). If you are familiar with Spark, you can also choose to use the [Azure Cosmos DB Spark connector](./nosql/quickstart-spark.md) to migrate data.
+Azure Cosmos DB migration strategies currently differ based on the API choice and the size of the data. To migrate smaller datasets – for validating data modeling, query performance, partition key choice etc. – you can use [Azure Data Factory’s Azure Cosmos DB connector](../data-factory/connector-azure-cosmos-db.md). If you are familiar with Spark, you can also choose to use the [Azure Cosmos DB Spark connector](./nosql/quickstart-spark.md) to migrate data.
 
 ## Challenges for large-scale migrations 
 

articles/cosmos-db/migration-choices.md

@@ -45,7 +45,6 @@ If you need help with capacity planning, consider reading our [guide to estimati
 |Migration type|Solution|Supported sources|Supported targets|Considerations|
 |---------|---------|---------|---------|---------|
 |Offline|[Intra-account container copy](intra-account-container-copy.md)|Azure Cosmos DB for NoSQL|Azure Cosmos DB for NoSQL|&bull; CLI-based; No set up needed. <br/>&bull; Supports large datasets.|
-|Offline|[Data Migration Tool](import-data.md)| &bull;JSON/CSV Files<br/>&bull;Azure Cosmos DB for NoSQL<br/>&bull;MongoDB<br/>&bull;SQL Server<br/>&bull;Table Storage<br/>&bull;AWS DynamoDB<br/>&bull;Azure Blob Storage|&bull;Azure Cosmos DB for NoSQL<br/>&bull;Azure Cosmos DB Tables API<br/>&bull;JSON Files |&bull; Easy to set up and supports multiple sources. <br/>&bull; Not suitable for large datasets.|
 |Offline|[Azure Data Factory](../data-factory/connector-azure-cosmos-db.md)| &bull;JSON/CSV Files<br/>&bull;Azure Cosmos DB for NoSQL<br/>&bull;Azure Cosmos DB for MongoDB<br/>&bull;MongoDB <br/>&bull;SQL Server<br/>&bull;Table Storage<br/>&bull;Azure Blob Storage <br/> <br/>See the [Azure Data Factory](../data-factory/connector-overview.md) article for other supported sources.|&bull;Azure Cosmos DB for NoSQL<br/>&bull;Azure Cosmos DB for MongoDB<br/>&bull;JSON Files <br/><br/> See the [Azure Data Factory](../data-factory/connector-overview.md) article for other supported targets. |&bull; Easy to set up and supports multiple sources.<br/>&bull; Makes use of the Azure Cosmos DB bulk executor library. <br/>&bull; Suitable for large datasets. <br/>&bull; Lack of checkpointing - It means that if an issue occurs during the course of migration, you need to restart the whole migration process.<br/>&bull; Lack of a dead letter queue - It means that a few erroneous files can stop the entire migration process.|
 |Offline|[Azure Cosmos DB Spark connector](./nosql/quickstart-spark.md)|Azure Cosmos DB for NoSQL. <br/><br/>You can use other sources with additional connectors from the Spark ecosystem.| Azure Cosmos DB for NoSQL. <br/><br/>You can use other targets with additional connectors from the Spark ecosystem.| &bull; Makes use of the Azure Cosmos DB bulk executor library. <br/>&bull; Suitable for large datasets. <br/>&bull; Needs a custom Spark setup. <br/>&bull; Spark is sensitive to schema inconsistencies and this can be a problem during migration. |
 |Online|[Azure Cosmos DB Spark connector + Change Feed](https://github.com/Azure/azure-sdk-for-java/tree/main/sdk/cosmos/azure-cosmos-spark_3_2-12/Samples/DatabricksLiveContainerMigration)|Azure Cosmos DB for NoSQL. <br/><br/>Uses Azure Cosmos DB Change Feed to stream all historic data as well as live updates.| Azure Cosmos DB for NoSQL. <br/><br/>You can use other targets with additional connectors from the Spark ecosystem.| &bull; Makes use of the Azure Cosmos DB bulk executor library. <br/>&bull; Suitable for large datasets. <br/>&bull; Needs a custom Spark setup. <br/>&bull; Spark is sensitive to schema inconsistencies and this can be a problem during migration. |
@@ -94,10 +93,6 @@ If you need help with capacity planning, consider reading our [guide to estimati
 
 For APIs other than the API for NoSQL, API for MongoDB and the API for Cassandra, there are various tools supported by each of the API's existing ecosystems. 
 
-**API for Table** 
-
-* [Data Migration Tool](table/import.md#data-migration-tool)
-
 **API for Gremlin**
 
 * [Graph bulk executor library](gremlin/bulk-executor-dotnet.md)