|
10 | 10 | ms.custom: include file
|
11 | 11 | ---
|
12 | 12 |
|
13 |
| -You can now use the Data Explorer tool in the Azure portal to create a database and collection. |
| 13 | +You can now use the Data Explorer tool in the Azure portal to create a database and container. |
14 | 14 |
|
15 |
| -1. Click **Data Explorer** > **New Collection**. |
| 15 | +1. Click **Data Explorer** > **New Container**. |
16 | 16 |
|
17 |
| - The **Add Collection** area is displayed on the far right, you may need to scroll right to see it. |
| 17 | + The **Add Container** area is displayed on the far right, you may need to scroll right to see it. |
18 | 18 |
|
19 |
| -  |
| 19 | +  |
20 | 20 |
|
21 |
| -2. In the **Add collection** page, enter the settings for the new collection. |
| 21 | +2. In the **Add container** page, enter the settings for the new container. |
22 | 22 |
|
23 |
| - Setting|Suggested value|Description |
24 |
| - ---|---|--- |
25 |
| - Database id|*Tasks*|Enter *Tasks* as the name for the new database. Database names must contain from 1 through 255 characters, and they cannot contain /, \\, #, ?, or a trailing space. |
26 |
| - Collection id|*Items*|Enter *Items* as the name for your new collection. Collection ids have the same character requirements as database names. |
27 |
| - Provision database throughput|Leave blank|Azure Cosmos DB can provision throughput at either the database level (all collections in a database share the same throughput) or at the collection level. Leave blank to provision throughput at the collection level for this particular collection. |
28 |
| - Storage capacity|*Unlimited*|Choose the Storage capacity of **Unlimited**. |
29 |
| - Partition key|*/category*|Enter "/category" as the partition key. Setting a partition key allows Azure Cosmos DB to scale your collection to meet the storage and throughput needs of your application. In general, a good choice of partition key is one that has a wide range of distinct values, and results in an even distribution of storage and request volume across your workload. [Learn more about partitioning.](../articles/cosmos-db/partitioning-overview.md) |
30 |
| - Throughput|*400 RU/s*|Change the throughput to 400 request units per second (RU/s). If you want to reduce latency, you can scale up the throughput later. |
| 23 | + |Setting|Suggested value|Description |
| 24 | + |---|---|---| |
| 25 | + |**Database ID**|Tasks|Enter *Tasks* as the name for the new database. Database names must contain from 1 through 255 characters, and they cannot contain /, \\, #, ?, or a trailing space. Check the **Provision database throughput** option, it allows you to share the throughput provisioned to the database across all the containers within the database. This option also helps with cost savings. | |
| 26 | + |**Throughput**|400|Leave the throughput at 400 request units per second (RU/s). If you want to reduce latency, you can scale up the throughput later.| |
| 27 | + |**Container ID**|Items|Enter *Items* as the name for your new container. Container IDs have the same character requirements as database names.| |
| 28 | + |**Partition key**| /category| The sample described in this article uses */category* as the partition key. Setting a partition key allows Azure Cosmos DB to scale your collection to meet the storage and throughput needs of your application. In general, a good choice of partition key is one that has a wide range of distinct values, and results in an even distribution of storage and request volume across your workload. [Learn more about partitioning.](../articles/cosmos-db/partitioning-overview.md)| |
31 | 29 |
|
32 |
| - In addition to the preceding settings, you can optionally add **Unique keys** for the collection. Let's leave the field empty in this example. Unique keys provide developers with the ability to add a layer of data integrity to the database. By creating a unique key policy while creating a collection, you ensure the uniqueness of one or more values per partition key. To learn more, refer to the [Unique keys in Azure Cosmos DB](../articles/cosmos-db/unique-keys.md) article. |
| 30 | + In addition to the preceding settings, you can optionally add **Unique keys** for the container. Let's leave the field empty in this example. Unique keys provide developers with the ability to add a layer of data integrity to the database. By creating a unique key policy while creating a container, you ensure the uniqueness of one or more values per partition key. To learn more, refer to the [Unique keys in Azure Cosmos DB](../articles/cosmos-db/unique-keys.md) article. |
33 | 31 |
|
34 |
| - Click **OK**. |
| 32 | + Select **OK**. Data Explorer displays the new database and container. |
35 | 33 |
|
36 |
| - Data Explorer displays the new database and collection. |
37 |
| - |
38 |
| -  |
0 commit comments