You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/cosmos-db/includes/cosmos-nosql-create-assign-roles.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -12,7 +12,7 @@ ms.custom: include file
12
12
13
13
When developing locally with passwordless authentication, make sure the user account that connects to Cosmos DB is assigned a role with the correct permissions to perform data operations. Currently, Azure Cosmos DB for NoSQL doesn't include built-in roles for data operations, but you can create your own using the Azure CLI or PowerShell.
14
14
15
-
Roles consist of a collection of permissions or actions that a user is allowed to perform, such as read, write, and delete. You can read more about [configuring role-based access control (RBAC)](../../../articles/cosmos-db/how-to-setup-rbac.md) in the Cosmos DB security configuration documentation.
15
+
Roles consist of a collection of permissions or actions that a user is allowed to perform, such as read, write, and delete. You can read more about [configuring role-based access control (RBAC)](../how-to-setup-rbac.md) in the Cosmos DB security configuration documentation.
If you don't have an [Azure subscription](../../guides/developer/azure-developer-guide.md#understanding-accounts-subscriptions-and-billing), create a [free account](https://azure.microsoft.com/free/java) before you begin.
Copy file name to clipboardExpand all lines: articles/cosmos-db/includes/storage-table-cosmos-comparison.md
+4-4Lines changed: 4 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -14,10 +14,10 @@ If you currently use Azure Table Storage, you gain the following benefits by mov
14
14
|Feature | Azure Table Storage | Azure Cosmos DB for Table |
15
15
| --- | --- | --- |
16
16
| Latency | Fast, but no upper bounds on latency. | Single-digit millisecond latency for reads and writes, backed with <10-ms latency reads and <15-ms latency writes at the 99th percentile, at any scale, anywhere in the world. |
17
-
| Throughput | Variable throughput model. Tables have a scalability limit of 20,000 operations per second. | Highly scalable with [dedicated reserved throughput per table](../articles/cosmos-db/request-units.md) that's backed by SLAs. Accounts have no upper limit on throughput and support >10 million operations per second per table in provisioned throughput mode. |
18
-
| Global distribution | Single region with one optional readable secondary read region for high availability that supports automatic and manual account failover. |[Turnkey global distribution](../articles/cosmos-db/distribute-data-globally.md) from one to 30+ regions. Support for [service-managed and manual failovers](../articles/cosmos-db/high-availability.md) at any time, anywhere in the world. |
17
+
| Throughput | Variable throughput model. Tables have a scalability limit of 20,000 operations per second. | Highly scalable with [dedicated reserved throughput per table](../request-units.md) that's backed by SLAs. Accounts have no upper limit on throughput and support >10 million operations per second per table in provisioned throughput mode. |
18
+
| Global distribution | Single region with one optional readable secondary read region for high availability that supports automatic and manual account failover. |[Turnkey global distribution](../distribute-data-globally.md) from one to 30+ regions. Support for [service-managed and manual failovers](../high-availability.md) at any time, anywhere in the world. |
19
19
| Indexing | Only primary index on `PartitionKey` and `RowKey`. No secondary indexes. | Automatic and complete indexing on all properties, no index management. |
20
20
| Query | Query execution uses index for primary key, and scans otherwise. | Queries can take advantage of automatic indexing on properties for fast query times. |
21
-
| Consistency | Strong within primary region. Eventual within secondary region. |[Five well-defined consistency levels](../articles/cosmos-db/consistency-levels.md) to trade off availability, latency, throughput, and consistency based on your application needs. |
22
-
| Pricing | Consumption-based. | Available in both [consumption-based](../articles/cosmos-db/serverless.md) and [provisioned capacity](../articles/cosmos-db/set-throughput.md) modes. |
21
+
| Consistency | Strong within primary region. Eventual within secondary region. |[Five well-defined consistency levels](../consistency-levels.md) to trade off availability, latency, throughput, and consistency based on your application needs. |
22
+
| Pricing | Consumption-based. | Available in both [consumption-based](../serverless.md) and [provisioned capacity](../set-throughput.md) modes. |
23
23
| SLAs | 99.99% availability. | 99.99% availability SLA for all single region accounts and all multi-region accounts with relaxed consistency, and 99.999% read availability on all multi-region database accounts [Industry-leading comprehensive SLAs](https://azure.microsoft.com/support/legal/sla/cosmos-db/) on general availability. |
This guide shows you common scenarios by using the Azure Table storage service or Azure Cosmos DB for Table. The samples are written in C++ and use the [Azure Storage Client Library for C++](https://github.com/Azure/azure-storage-cpp/blob/master/README.md). This article covers the following scenarios:
0 commit comments