Skip to content

Commit 525daf3

Browse files
authored
Merge pull request #108462 from timsander1/master
update mongodb connection screenshots
2 parents 3b49573 + d2b07e6 commit 525daf3

File tree

7 files changed

+34
-35
lines changed

7 files changed

+34
-35
lines changed
-1.7 KB
Loading
-1.64 KB
Loading
-1.64 KB
Loading

articles/cosmos-db/mongodb-compass.md

Lines changed: 9 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -4,42 +4,43 @@ description: Learn how to use MongoDB Compass to store and manage data in Azure
44
ms.service: cosmos-db
55
ms.subservice: cosmosdb-mongo
66
ms.topic: conceptual
7-
ms.date: 06/24/2019
7+
ms.date: 03/20/2020
88
author: LuisBosquez
99
ms.author: lbosq
1010
---
1111

12-
# Use MongoDB Compass to connect to Azure Cosmos DB's API for MongoDB
12+
# Use MongoDB Compass to connect to Azure Cosmos DB's API for MongoDB
1313

14-
This tutorial demonstrates how to use [MongoDB Compass](https://www.mongodb.com/products/compass) when storing and/or managing data in Cosmos DB. We use the Azure Cosmos DB's API for MongoDB for this walk-through. For those of you unfamiliar, Compass is a GUI for MongoDB. It is commonly used to visualize your data, run ad-hoc queries, along with managing your data.
14+
This tutorial demonstrates how to use [MongoDB Compass](https://www.mongodb.com/products/compass) when storing and/or managing data in Cosmos DB. We use the Azure Cosmos DB's API for MongoDB for this walk-through. For those of you unfamiliar, Compass is a GUI for MongoDB. It is commonly used to visualize your data, run ad-hoc queries, along with managing your data.
1515

1616
Cosmos DB is Microsoft's globally distributed multi-model database service. You can quickly create and query document, key/value, and graph databases, all of which benefit from the global distribution and horizontal scale capabilities at the core of Cosmos DB.
1717

18+
## Pre-requisites
1819

19-
## Pre-requisites
2020
To connect to your Cosmos DB account using Robo 3T, you must:
2121

2222
* Download and install [Compass](https://www.mongodb.com/download-center/compass?jmp=hero)
2323
* Have your Cosmos DB [connection string](connect-mongodb-account.md) information
2424

25-
## Connect to Cosmos DB's API for MongoDB
25+
## Connect to Cosmos DB's API for MongoDB
26+
2627
To connect your Cosmos DB account to Compass, you can follow the below steps:
2728

2829
1. Retrieve the connection information for your Cosmos account configured with Azure Cosmos DB's API MongoDB using the instructions [here](connect-mongodb-account.md).
2930

3031
![Screenshot of the connection string blade](./media/mongodb-compass/mongodb-compass-connection.png)
3132

32-
2. Click on the button that says **Copy to clipboard** next to your **Primary/Secondary connection string** in Cosmos DB. Clicking this button will copy your entire connection string to your clipboard.
33+
2. Click on the button that says **Copy to clipboard** next to your **Primary/Secondary connection string** in Cosmos DB. Clicking this button will copy your entire connection string to your clipboard.
3334

3435
![Screenshot of the copy to clipboard button](./media/mongodb-compass/mongodb-connection-copy.png)
3536

36-
3. Open Compass on your desktop/machine and click on **Connect** and then **Connect to...**.
37+
3. Open Compass on your desktop/machine and click on **Connect** and then **Connect to...**.
3738

3839
4. Compass will automatically detect a connection string in the clipboard, and will prompt to ask whether you wish to use that to connect. Click on **Yes** as shown in the screenshot below.
3940

4041
![Screenshot of the Compass prompt to connect](./media/mongodb-compass/mongodb-compass-detect.png)
4142

42-
5. Upon clicking **Yes** in the above step, your details from the connection string will be automatically populated. Remove the value automatically populated in the **Replica Set Name** field to ensure that is left blank.
43+
5. Upon clicking **Yes** in the above step, your details from the connection string will be automatically populated. Remove the value automatically populated in the **Replica Set Name** field to ensure that is left blank.
4344

4445
![Screenshot of the Compass prompt to connect](./media/mongodb-compass/mongodb-compass-replica.png)
4546

articles/cosmos-db/mongodb-mongochef.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -4,9 +4,9 @@ description: Learn how to connect to an Azure Cosmos DB's API for MongoDB using
44
ms.service: cosmos-db
55
ms.subservice: cosmosdb-mongo
66
ms.topic: conceptual
7-
ms.date: 11/01/2019
8-
author: sivethe
9-
ms.author: sivethe
7+
ms.date: 03/20/2020
8+
author: timsander1
9+
ms.author: tisande
1010
ms.custom: seodec18
1111
---
1212
# Connect to an Azure Cosmos account using Studio 3T

articles/cosmos-db/mongodb-mongoose.md

Lines changed: 4 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -5,9 +5,9 @@ ms.service: cosmos-db
55
ms.subservice: cosmosdb-mongo
66
ms.devlang: nodejs
77
ms.topic: conceptual
8-
ms.date: 11/18/2019
9-
author: sivethe
10-
ms.author: sivethe
8+
ms.date: 03/20/2020
9+
author: timsander1
10+
ms.author: tisande
1111
ms.custom: seodec18
1212
---
1313
# Connect a Node.js Mongoose application to Azure Cosmos DB
@@ -54,6 +54,7 @@ Let's create a Cosmos account. If you already have an account you want to use, y
5454
> The ```--save``` flag adds the dependency to the package.json file.
5555
5656
1. Import the dependencies in your index.js file.
57+
5758
```JavaScript
5859
var mongoose = require('mongoose');
5960
var env = require('dotenv').config(); //Use the .env file to load the variables
Lines changed: 18 additions & 21 deletions
Original file line numberDiff line numberDiff line change
@@ -1,58 +1,60 @@
11
---
2-
title: Post-migration optimization steps with Azure Cosmos DBs API for MongoDB
2+
title: Post-migration optimization steps with Azure Cosmos DB's API for MongoDB
33
description: This doc provides the post-migration optimization techniques from MongoDB to Azure Cosmos DB's APi for Mongo DB.
44
author: LuisBosquez
55
ms.service: cosmos-db
66
ms.subservice: cosmosdb-mongo
77
ms.topic: conceptual
8-
ms.date: 04/18/2019
8+
ms.date: 03/20/2020
99
ms.author: lbosq
1010

1111
---
1212

13-
# Post-migration optimization steps when using Azure Cosmos DBs API for MongoDB
13+
# Post-migration optimization steps when using Azure Cosmos DB's API for MongoDB
1414

15-
After you migrate the data stored in MongoDB database to Azure Cosmos DBs API for MongoDB, you can connect to Azure Cosmos DB and manage the data. This guide provides the steps you should consider after the migration. See the [Migrate MongoDB to Azure Cosmos DBs API for MongoDB tutorial](../dms/tutorial-mongodb-cosmos-db.md) for the migration steps.
15+
After you migrate the data stored in MongoDB database to Azure Cosmos DB's API for MongoDB, you can connect to Azure Cosmos DB and manage the data. This guide provides the steps you should consider after the migration. See the [Migrate MongoDB to Azure Cosmos DB's API for MongoDB tutorial](../dms/tutorial-mongodb-cosmos-db.md) for the migration steps.
1616

1717
In this guide, you will learn how to:
18-
- [Connect your application](#connect-account)
19-
- [Optimize the indexing policy](#indexing)
20-
- [Configure global distribution for Azure Cosmos DB's API for MongoDB](#distribute-data)
21-
- [Set consistency level](#consistency)
18+
19+
- [Connect your application](#connect-your-application)
20+
- [Optimize the indexing policy](#optimize-the-indexing-policy)
21+
- [Configure global distribution for Azure Cosmos DB's API for MongoDB](#globally-distribute-your-data)
22+
- [Set consistency level](#set-consistency-level)
2223

2324
> [!NOTE]
2425
> The only mandatory post-migration step on your application level is changing the connection string in your application to point to your new Azure Cosmos DB account. All other migration steps are recommended optimizations.
2526
>
2627
27-
## <a id="connect-account"></a>Connect your application
28+
## Connect your application
2829

2930
1. In a new window sign into the [Azure portal](https://www.portal.azure.com/)
3031
2. From the [Azure portal](https://www.portal.azure.com/), in the left pane open the **All resources** menu and find the Azure Cosmos DB account to which you have migrated your data.
3132
3. Open the **Connection String** blade. The right pane contains all the information that you need to successfully connect to your account.
32-
4. Use the connection information in your application's configuration (or other relevant places) to reflect the Azure Cosmos DB's API for MongoDB connection in your app.
33+
4. Use the connection information in your application's configuration (or other relevant places) to reflect the Azure Cosmos DB's API for MongoDB connection in your app.
3334
![Connection-String](./media/mongodb-post-migration/connection-string.png)
3435

3536
For more details, please see the [Connect a MongoDB application to Azure Cosmos DB](connect-mongodb-account.md) page.
3637

37-
## <a id="indexing"></a>Optimize the indexing policy
38+
## Optimize the indexing policy
3839

3940
All data fields are automatically indexed, by default, during the migration of data to Azure Cosmos DB. In many cases, this default indexing policy is acceptable. In general, removing indexes optimizes write requests and having the default indexing policy (i.e., automatic indexing) optimizes read requests.
4041

4142
For more information on indexing, see [Data indexing in Azure Cosmos DB's API for MongoDB](mongodb-indexing.md) as well as the [Indexing in Azure Cosmos DB](index-overview.md) articles.
4243

43-
## <a id="distribute-data"></a>Globally distribute your data
44+
## Globally distribute your data
4445

4546
Azure Cosmos DB is available in all [Azure regions](https://azure.microsoft.com/regions/#services) worldwide. After selecting the default consistency level for your Azure Cosmos DB account, you can associate one or more Azure regions (depending on your global distribution needs). For high availability and business continuity, we always recommend running in at least 2 regions. You can review the tips for [optimizing cost of multi-region deployments in Azure Cosmos DB](optimize-cost-regions.md).
4647

47-
To globally distribute your data, please see [Distribute data globally on Azure Cosmos DB’s API for MongoDB](tutorial-global-distribution-mongodb.md).
48+
To globally distribute your data, please see [Distribute data globally on Azure Cosmos DB's API for MongoDB](tutorial-global-distribution-mongodb.md).
49+
50+
## Set consistency level
4851

49-
## <a id="consistency"></a>Set consistency level
5052
Azure Cosmos DB offers 5 well-defined [consistency levels](consistency-levels.md). To read about the mapping between MongoDB and Azure Cosmos DB consistency levels, read [Consistency levels and Azure Cosmos DB APIs](consistency-levels-across-apis.md). The default consistency level is the session consistency level. Changing the consistency level is optional and you can optimize it for your app. To change consistency level using Azure portal:
5153

5254
1. Go to the **Default Consistency** blade under Settings.
5355
2. Select your [consistency level](consistency-levels.md)
5456

55-
Most users leave their consistency level at the default session consistency setting. However, there are [availability and performance tradeoffs for various consistency levels](consistency-levels-tradeoffs.md).
57+
Most users leave their consistency level at the default session consistency setting. However, there are [availability and performance tradeoffs for various consistency levels](consistency-levels-tradeoffs.md).
5658

5759
## Next steps
5860

@@ -62,9 +64,4 @@ Most users leave their consistency level at the default session consistency sett
6264
* [Expire data with Azure Cosmos DB's API for MongoDB](mongodb-time-to-live.md)
6365
* [Consistency Levels in Azure Cosmos DB](consistency-levels.md)
6466
* [Indexing in Azure Cosmos DB](index-overview.md)
65-
* [Request Units in Azure Cosmos DB](request-units.md)
66-
67-
68-
69-
70-
67+
* [Request Units in Azure Cosmos DB](request-units.md)

0 commit comments

Comments
 (0)