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/nosql/how-to-change-capacity-mode.md
+5-4Lines changed: 5 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -14,14 +14,15 @@ ms.custom: build-2024
14
14
15
15
[!INCLUDE[NoSQL](../includes/appliesto-nosql.md)]
16
16
17
-
Azure Cosmos DB allows a user to change the capacity mode of an account from serverless to provisioned capacity. Changing from serverless to provisioned capacity mode converts all containers within the account to manual provisioned throughput containers in-place. The containers' throughput is determined according to the following formula.
17
+
Azure Cosmos DB allows a user to change the capacity mode of an account from serverless to provisioned capacity. Changing from serverless to provisioned capacity mode converts all containers within the account to manual provisioned throughput containers in-place. The containers' throughput is approximately determined according to the following formula.
18
18
19
-
`Throughput(RU/s) = max(5000, StorageInGB * 10)`
19
+
`Throughput(RU/s) = max(5000, number of partitions (physical) * 1000)`
20
20
21
21
Users can also change the throughput or provisioning mode from manual to autoscale once the migration is complete.
22
22
23
23
>[!Caution]
24
-
>This is an irreversible operation. Once migrated, the capacity mode can't be changed back to serverless.
24
+
> This is an irreversible operation. Once migrated, the capacity mode can't be changed back to serverless.
25
+
> The throughput calculation and default provisioning mode (manual) is subject to change in future.
25
26
26
27
## Getting started
27
28
@@ -39,7 +40,7 @@ Follow the steps below to change the capacity mode using Azure portal.
39
40
40
41
4. Once the migration is complete, the capacity mode will be changed to **provisioned capacity**.
41
42
42
-
>[!Note]
43
+
>[!Note]
43
44
> There are no SLA's associated with the duration of the capacity mode change.
44
45
> Users cannot execute any management operation while the migration is in progress. However, the containers can be accessed as usual by any client application.
0 commit comments