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/reserved-capacity.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
@@ -124,17 +124,17 @@ Imagine this hypothetical scenario: A company is working on a new application bu
124
124
* Total of 800 RU/s: eight units of the 100 RU/s option, with a 20% discount.
125
125
* Scoped to the development resource group.
126
126
* One year term, since the project lasts for nine months.
127
-
*Paid upfront, since it's a small value.
127
+
*They paid upfront, it's a small value.
128
128
* On day 30 they purchased reserved capacity for their tests environment:
129
129
* 750,000 RU/s: 7,500 units of the 100 RU/s option, with a 20% discount.
130
130
* Scoped to the test subscription.
131
131
* One year term.
132
-
*Paid monthly.
132
+
*They choose to pay monthly.
133
133
* On day 180 they purchased reserved capacity for the production environment:
134
134
* 3,500,000 RU/s: One unit of the 3,000,000 RU/s option, with a 43.2% discount. And 5,000 units of the 100 RU/s option, with a 20% discount.
135
135
* Scoped to the production subscription.
136
136
* Three-years term, to maximize the discounts.
137
-
*Paid Monthly.
137
+
*They choose to pay monthly too.
138
138
139
139
## Sample scenario 2
140
140
@@ -233,7 +233,7 @@ The reservation discount is applied automatically to the Azure Cosmos DB resourc
233
233
*[Azure reservations in the Partner Center CSP program](/partner-center/azure-reservations)
234
234
235
235
Trying to do capacity planning for a migration to Azure Cosmos DB? You can use information about your existing database cluster for capacity planning.
236
-
* 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)
236
+
* 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)
237
237
* If you know typical request rates for your current database workload, read about [estimating request units using Azure Cosmos DB capacity planner](estimate-ru-with-capacity-planner.md)
0 commit comments