Skip to content

Commit d112830

Browse files
authored
Merge pull request #281065 from MicrosoftDocs/main
Publish to Live Wednesday 4AM PST 7/17
2 parents f02357a + abdeca3 commit d112830

17 files changed

+98
-135
lines changed

articles/app-service/quickstart-dotnetcore.md

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -13,6 +13,7 @@ author: cephalin
1313
ms.author: cephalin
1414
ms.custom: devx-track-csharp, mvc, devcenter, vs-azure, devdivchpfy22, devx-track-azurepowershell, devx-track-dotnet, ai-video-demo, devx-track-extended-azdevcli
1515
ai-usage: ai-assisted
16+
ms.collection: ce-skilling-ai-copilot
1617
---
1718

1819
<!-- NOTES:

articles/app-service/tutorial-dotnetcore-sqldb-app.md

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -10,6 +10,7 @@ ms.devlang: csharp
1010
ms.service: app-service
1111
ms.custom: devx-track-csharp, mvc, cli-validate, devdivchpfy22, service-connector, devx-track-dotnet, AppServiceConnectivity
1212
zone_pivot_groups: app-service-portal-azd
13+
ms.collection: ce-skilling-ai-copilot
1314
---
1415

1516
# Tutorial: Deploy an ASP.NET Core and Azure SQL Database app to Azure App Service

articles/app-service/tutorial-java-tomcat-mysql-app.md

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -8,6 +8,7 @@ ms.topic: tutorial
88
ms.date: 05/08/2024
99
ms.custom: mvc, devx-track-extended-java, AppServiceConnectivity, devx-track-extended-azdevcli, linux-related-content
1010
zone_pivot_groups: app-service-portal-azd
11+
ms.collection: ce-skilling-ai-copilot
1112
---
1213

1314
# Tutorial: Build a Tomcat web app with Azure App Service on Linux and MySQL
Lines changed: 29 additions & 16 deletions
Original file line numberDiff line numberDiff line change
@@ -1,24 +1,30 @@
11
---
22
title: Options to migrate data from MongoDB
3-
titleSuffix: Azure Cosmos DB for MongoDB vCore
4-
description: Review various options to migrate your data from other MongoDB sources to Azure Cosmos DB for MongoDB vCore.
3+
titleSuffix: vCore-based Azure Cosmos DB for MongoDB
4+
description: Review various options to migrate your data from other MongoDB sources to vCore-based Azure Cosmos DB for MongoDB.
55
author: sandeep-nair
66
ms.author: sandnair
77
ms.reviewer: sidandrews
88
ms.service: cosmos-db
99
ms.subservice: mongodb-vcore
1010
ms.topic: conceptual
1111
ms.date: 11/17/2023
12-
# CustomerIntent: As a MongoDB user, I want to understand the various options available to migrate my data to Azure Cosmos DB for MongoDB vCore, so that I can make an informed decision about which option is best for my use case.
12+
# CustomerIntent: As a MongoDB user, I want to understand the various options available to migrate my data to vCore-based Azure Cosmos DB for MongoDB, so that I can make an informed decision about which option is best for my use case.
1313
---
1414

15-
# What are the options to migrate data from MongoDB to Azure Cosmos DB for MongoDB vCore?
15+
# What are the options to migrate data from MongoDB to vCore-based Azure Cosmos DB for MongoDB?
1616

17-
This document describes the various options to lift and shift your MongoDB workloads to Azure Cosmos DB for MongoDB vCore offering.
17+
This document describes the various options to lift and shift your MongoDB workloads to vCore-based Azure Cosmos DB for MongoDB offering.
18+
19+
Migrations can be done in two ways:
20+
21+
- Offline Migration: A snapshot based bulk copy from source to target. New data added/updated/deleted on the source after the snapshot isn't copied to the target. The application downtime required depends on the time taken for the bulk copy activity to complete.
22+
23+
- Online Migration: Apart from the bulk data copy activity done in the offline migration, a change stream monitors all additions/updates/deletes. After the bulk data copy is completed, the data in the change stream is copied to the target to ensure that all updates made during the migration process are also transferred to the target. The application downtime required is minimal.
1824

1925
## Azure Data Studio (Online)
2026

21-
The [The MongoDB migration extension for Azure Data Studio](/azure-data-studio/extensions/database-migration-for-mongo-extension) is the preferred tool in migrating your MongoDB workloads to the API for MongoDB vCore.
27+
The [MongoDB migration extension for Azure Data Studio](/azure-data-studio/extensions/database-migration-for-mongo-extension) is the preferred tool in migrating your MongoDB workloads to the vCore-based Azure Cosmos DB for MongoDB.
2228

2329
The migration process has two phases:
2430

@@ -38,7 +44,7 @@ Use the graphical user interface to manage the entire migration process from st
3844

3945
## Native MongoDB tools (Offline)
4046

41-
You can use the native MongoDB tools such as *mongodump/mongorestore*, *mongoexport/mongoimport* to migrate datasets offline (without replicating live changes) to Azure Cosmos DB for MongoDB vCore offering.
47+
You can use the native MongoDB tools such as *mongodump/mongorestore*, *mongoexport/mongoimport* to migrate datasets offline (without replicating live changes) to vCore-based Azure Cosmos DB for MongoDB offering.
4248

4349
| Scenario | MongoDB native tool |
4450
| --- | --- |
@@ -47,23 +53,30 @@ You can use the native MongoDB tools such as *mongodump/mongorestore*, *mongoexp
4753

4854
- *mongoexport/mongoimport* is the best pair of migration tools for migrating a subset of your MongoDB database.
4955
- *mongoexport* exports your existing data to a human-readable JSON or CSV file. *mongoexport* takes an argument specifying the subset of your existing data to export.
50-
- *mongoimport* opens a JSON or CSV file and inserts the content into the target database instance (Azure Cosmos DB for MongoDB vCore in this case.).
51-
- JSON and CSV aren't a compact format; you could incur excess network charges as *mongoimport* sends data to Azure Cosmos DB for MongoDB vCore.
52-
- *mongodump/mongorestore* is the best pair of migration tools for migrating your entire MongoDB database. The compact BSON format makes more efficient use of network resources as the data is inserted into Azure Cosmos DB for MongoDB vCore.
56+
- *mongoimport* opens a JSON or CSV file and inserts the content into the target database instance (vCore-based Azure Cosmos DB for MongoDB in this case.).
57+
- JSON and CSV aren't a compact format; you could incur excess network charges as *mongoimport* sends data to vCore-based Azure Cosmos DB for MongoDB.
58+
- *mongodump/mongorestore* is the best pair of migration tools for migrating your entire MongoDB database. The compact BSON format makes more efficient use of network resources as the data is inserted into vCore-based Azure Cosmos DB for MongoDB.
5359
- *mongodump* exports your existing data as a BSON file.
54-
- *mongorestore* imports your BSON file dump into Azure Cosmos DB for MongoDB vCore.
60+
- *mongorestore* imports your BSON file dump into vCore-based Azure Cosmos DB for MongoDB.
5561

5662
> [!NOTE]
5763
> The MongoDB native tools can move data only as fast as the host hardware allows.
5864
5965
## Data migration using Azure Databricks (Offline/Online)
6066

61-
Migrating using Azure Databricks offers full control of the migration rate and data transformation. This method can also support large datasets that are in TBs in size.
67+
Migrating using Azure Databricks offers full control of the migration rate and data transformation. This method can also support large datasets that are in TBs in size. The spark migration utility operates as a job within Databricks.
68+
69+
70+
This tool supports the following MongoDB sources:
71+
- MongoDB VM
72+
- MongoDB Atlas
73+
- AWS DocumentDB
74+
- Azure Cosmos DB MongoDB RU (Offline only)
75+
76+
[Sign up for Azure Cosmos DB for MongoDB Spark Migration](https://forms.office.com/r/cLSRNugFSp) to gain access to the Spark Migration Tool GitHub repository. The repository offers detailed, step-by-step instructions for migrating your workloads from various Mongo sources to vCore-based Azure Cosmos DB for MongoDB.
6277

63-
- [Azure Databricks](https://azure.microsoft.com/services/databricks/) is a platform as a service (PaaS) offering for [Apache Spark](https://spark.apache.org/). You can use Azure Databricks to do an offline/online migration of databases from MongoDB to Azure Cosmos DB for MongoDB.
64-
- Here's how you can [migrate data to Azure Cosmos DB for MongoDB vCore offline using Azure Databricks](../migrate-databricks.md#provision-an-azure-databricks-cluster)
6578

6679
## Related content
6780

68-
- Migrate data to Azure Cosmos DB for MongoDB vCore [using native MongoDB tools](how-to-migrate-native-tools.md).
69-
- Migrate data to Azure Cosmos DB for MongoDB vCore [using Azure Databricks](../migrate-databricks.md).
81+
- Migrate data to vCore-based Azure Cosmos DB for MongoDB using [native MongoDB tools](how-to-migrate-native-tools.md).
82+
- Migrate data to vCore-based Azure Cosmos DB for MongoDB using the [MongoDB migration extension for Azure Data Studio](/azure-data-studio/extensions/database-migration-for-mongo-extension).

0 commit comments

Comments
 (0)