Skip to content

Commit c25d192

Browse files
author
Sandeep Nair
committed
Fixed next steps and links
1 parent 74eebb4 commit c25d192

File tree

1 file changed

+4
-10
lines changed

1 file changed

+4
-10
lines changed

articles/cosmos-db/mongodb/vcore/tutorial-mongotools-cosmos-db-vcore.md

Lines changed: 4 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -28,7 +28,7 @@ In this tutorial, you learn how to:
2828
2929
In this tutorial, you migrate a dataset in MongoDB hosted in an Azure Virtual Machine to Azure Cosmos DB for MongoDB vCore by using MongoDB native tools. The MongoDB native tools are a set of binaries that facilitate data manipulation on an existing MongoDB instance. The focus of this doc is on migrating data out of a MongoDB instance using *mongoexport/mongoimport* or *mongodump/mongorestore*. Since the native tools connect to MongoDB using connection strings, you can run the tools anywhere, however we recommend running these tools within the same network as the MongoDB instance to avoid firewall issues.
3030

31-
The MongoDB native tools can move data only as fast as the host hardware allows; the native tools can be the simplest solution for small datasets where total migration time isn't a concern. [MongoDB Spark connector](https://docs.mongodb.com/spark-connector/current/), [Azure Data Migration Service (DMS)](../../dms/tutorial-mongodb-cosmos-db.md), or [Azure Data Factory (ADF)](../../data-factory/connector-azure-cosmos-db-mongodb-api.md) can be better alternatives if you need a scalable migration pipeline.
31+
The MongoDB native tools can move data only as fast as the host hardware allows; the native tools can be the simplest solution for small datasets where total migration time isn't a concern. [MongoDB Spark connector](https://docs.mongodb.com/spark-connector/current/), [Azure Data Migration Service (DMS)](../../../dms/tutorial-mongodb-cosmos-db.md), or [Azure Data Factory (ADF)](../../../data-factory/connector-azure-cosmos-db-mongodb-api.md) can be better alternatives if you need a scalable migration pipeline.
3232

3333

3434
## Prerequisites
@@ -117,14 +117,8 @@ The rest of this section guides you through using the pair of tools you selected
117117
1. **Monitor** the terminal output from *mongorestore*. You should see that it prints lines to the terminal updating on the migration status:
118118
119119
120-
## Additional resources
121-
122-
* [Azure Cosmos DB for MongoDB vCore service information](https://azure.microsoft.com/services/cosmos-db/)
123-
* [MongoDB database tools documentation](https://docs.mongodb.com/database-tools/)
124-
* Trying to do capacity planning for a migration to Azure Cosmos DB for MongoDB vCore?
125-
* If all you know is the number of vcores and servers in your existing database cluster, read about [estimating request units using vCores or vCPUs](../convert-vcore-to-request-unit.md)
126-
* If you know typical request rates for your current database workload, read about [estimating request units using Azure Cosmos DB for MongoDB vCore capacity planner](estimate-ru-capacity-planner.md)
127-
128120
## Next steps
129121
130-
* Review migration guidance for additional scenarios in the Microsoft [Database Migration Guide](/data-migration/).
122+
- Read more about [feature compatibility with MongoDB](compatibility.md).
123+
- Get started by [creating an account](quickstart-portal.md).
124+

0 commit comments

Comments
 (0)