Skip to content

Commit de6c2bb

Browse files
Improve Acrolinx Clarity score
1 parent 4ac8682 commit de6c2bb

1 file changed

Lines changed: 8 additions & 8 deletions

File tree

articles/postgresql/single-server/concept-reserved-pricing.md

Lines changed: 8 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -22,7 +22,7 @@ Azure Database for PostgreSQL now helps you save money by prepaying for compute
2222

2323
## How does the instance reservation work?
2424

25-
You don't need to assign the reservation to specific Azure Database for PostgreSQL servers. An already running Azure Database for PostgreSQL (or ones that are newly deployed) will automatically get the benefit of reserved pricing. By purchasing a reservation, you're pre-paying for the compute costs for a period of one or three years. As soon as you buy a reservation, the Azure database for PostgreSQL compute charges that match the reservation attributes are no longer charged at the pay-as-you go rates. A reservation does not cover software, networking, or storage charges associated with the PostgreSQL Database servers. At the end of the reservation term, the billing benefit expires, and the Azure Database for PostgreSQL are billed at the pay-as-you go price. Reservations do not auto-renew. For pricing information, see the [Azure Database for PostgreSQL reserved capacity offering](https://azure.microsoft.com/pricing/details/postgresql/). </br>
25+
You don't need to assign the reservation to specific Azure Database for PostgreSQL servers. An already running Azure Database for PostgreSQL (or ones that are newly deployed) automatically gest the benefit of reserved pricing. By purchasing a reservation, you're pre-paying for the compute costs for one or three years. As soon as you buy a reservation, the Azure database for PostgreSQL compute charges that match the reservation attributes are no longer charged at the pay-as-you go rates. A reservation does not cover software, networking, or storage charges associated with the PostgreSQL Database servers. At the end of the reservation term, the billing benefit expires, and the Azure Database for PostgreSQL are billed at the pay-as-you go price. Reservations do not auto-renew. For pricing information, see the [Azure Database for PostgreSQL reserved capacity offering](https://azure.microsoft.com/pricing/details/postgresql/). </br>
2626

2727
> [!IMPORTANT]
2828
> Reserved capacity pricing is available for the Azure Database for PostgreSQL in [Single server](./overview.md#azure-database-for-postgresql---single-server) and [Flexible Server](../flexible-server/overview.md) deployment options.
@@ -41,13 +41,13 @@ You can exchange a reservation for another reservation of the same type, you can
4141

4242
## Reservation discount
4343

44-
You may save up to 65% on compute costs with reserved instances. In order to find the discount for your case, please visit the [Reservation blade on the Azure portal](https://aka.ms/reservations) and check the savings per pricing tier and per region. Reserved instances help you manage your workloads, budget, and forecast better with an upfront payment for a one-year or three-year term. You can also exchange or cancel reservations as business needs change.
44+
You may save up to 65% on compute costs with reserved instances. In order to find the discount for your case, visit the [Reservation blade on the Azure portal](https://aka.ms/reservations) and check the savings per pricing tier and per region. Reserved instances help you manage your workloads, budget, and forecast better with an upfront payment for a one-year or three-year term. You can also exchange or cancel reservations as business needs change.
4545

4646
## Determine the right server size before purchase
4747

48-
The size of reservation should be based on the total amount of compute used by the existing or soon-to-be-deployed servers within a specific region and using the same performance tier and hardware generation.</br>
48+
The size of reservation should be based on total amount of compute used by the existing, or soon-to-be-deployed, servers within a specific region, and using the same performance tier and hardware generation.</br>
4949

50-
For example, let's suppose that you are running one general purpose Gen5 – 32 vCore PostgreSQL database, and two memory-optimized Gen5 – 16 vCore PostgreSQL databases. Further, let's supposed that you plan to deploy within the next month an additional general purpose Gen5 – 8 vCore database server, and one memory-optimized Gen5 – 32 vCore database server. Let's suppose that you know that you will need these resources for at least one year. In this case, you should purchase a 40 (32 + 8) vCores, one-year reservation for single database general purpose - Gen5 and a 64 (2x16 + 32) vCore one year reservation for single database memory optimized - Gen5.
50+
For example, let's suppose that you are running one general purpose Gen5 – 32 vCore PostgreSQL database, and two memory-optimized Gen5 – 16 vCore PostgreSQL databases. Further, let's suppose that you plan to deploy an additional general purpose Gen5 – 8 vCore database server, and one memory-optimized Gen5 – 32 vCore database server within the next month. Let's suppose that you know that you need these resources for at least one year. In this case, you should purchase a 40 (32 + 8) vCores, one-year reservation for single database general purpose - Gen5 and a 64 (2x16 + 32) vCore one year reservation for single database memory optimized - Gen5.
5151

5252
## Buy Azure Database for PostgreSQL reserved capacity
5353

@@ -67,8 +67,8 @@ The following table describes required fields.
6767
| Region | The Azure region that’s covered by the Azure Database for PostgreSQL reserved capacity reservation.
6868
| Deployment Type | The Azure Database for PostgreSQL resource type that you want to buy the reservation for.
6969
| Performance Tier | The service tier for the Azure Database for PostgreSQL servers.
70-
| Term | This can be One year or Three years.
71-
| Quantity | The amount of compute resources being purchased within the Azure Database for PostgreSQL reserved capacity reservation. The quantity is a number of vCores in the selected Azure region and Performance tier that are being reserved and will get the billing discount. For example, if you are running or planning to run an Azure Database for PostgreSQL servers with the total compute capacity of Gen5 16 vCores in the East US region, then you would specify quantity as 16 to maximize the benefit for all servers.
70+
| Term | This term can be either One year or Three years.
71+
| Quantity | The amount of compute resources being purchased within the Azure Database for PostgreSQL reserved capacity reservation. Is the number of vCores in the selected Azure region and Performance tier that are being reserved and get the billing discount. For example, if you are running or planning to run an Azure Database for PostgreSQL servers with the total compute capacity of Gen5 16 vCores in the East US region, then you would specify quantity as 16 to maximize the benefit for all servers.
7272

7373
## Reserved instances API support
7474

@@ -85,15 +85,15 @@ For more information, see [APIs for Azure reservation automation](../../cost-man
8585

8686
## vCore size flexibility
8787

88-
vCore size flexibility helps you scale up or down within a performance tier and region, without losing the reserved capacity benefit. If you scale to higher vCores than your reserved capacity, you will be billed for the excess vCores using pay-as-you-go pricing.
88+
vCore size flexibility helps you scale up or down within a performance tier and region, without losing the reserved capacity benefit. If you scale to higher vCores than your reserved capacity, you are billed for the excess vCores using pay-as-you-go pricing.
8989

9090
## How to view reserved instance purchase details
9191

9292
You can view your reserved instance purchase details via the [Reservations](https://aka.ms/reservations) blade in the Azure portal.
9393

9494
## Reserved instance expiration
9595

96-
You'll receive email notifications, first one 30 days prior to reservation expiry and another one at expiration. Once the reservation expires, deployed VMs will continue to run and be billed at a pay-as-you-go rate.
96+
You receive email notifications, first one 30 days prior to reservation expiry and another one at expiration. Once the reservation expires, deployed VMs continue to run and are billed at a pay-as-you-go rate.
9797

9898
## Need help? Contact us
9999

0 commit comments

Comments
 (0)