Merge pull request #232301 from varun-dhawan/varund-novena

[PostgreSQL] updates the overview doc

Author: v-regandowner

articles/postgresql/.openpublishing.redirection.postgresql.json

@@ -1454,6 +1454,11 @@
         "source_path_from_root": "/articles/postgresql/flexible-server/application-best-practices.md",
         "redirect_url": "/azure/postgresql/flexible-server/overview",
         "redirect_document_id": false
+    },
+    {
+        "source_path_from_root": "/articles/postgresql/single-server/overview-postgres-choose-server-options.md",
+        "redirect_url": "/azure/postgresql/flexible-server/overview-postgres-choose-server-options",
+        "redirect_document_id": true
     }
     ]
 }

articles/postgresql/TOC.yml

@@ -5,7 +5,7 @@
   - name: What is Azure DB for PostgreSQL?
     href: single-server/overview.md
   - name: Which PostgreSQL deployment option to choose?
-    href: single-server/overview-postgres-choose-server-options.md
+    href: flexible-server/overview-postgres-choose-server-options.md
   - name: Service updates
     items:
     - name: SSL root certificate expiring

articles/postgresql/single-server/overview-postgres-choose-server-options.md renamed to articles/postgresql/flexible-server/overview-postgres-choose-server-options.md

@@ -2,40 +2,39 @@
 title: Choose the right PostgreSQL server option in Azure
 description: Provides guidelines for choosing the right PostgreSQL server option for your deployments.
 ms.service: postgresql
-ms.subservice: single-server
+ms.subservice: flexible-server
 ms.topic: overview
-ms.author: sunila
-author: sunilagarwal
+author: varun-dhawan
+ms.author: varundhawan
 ms.custom: mvc, ignite-2022
-ms.date: 06/24/2022
+ms.date: 03/27/2023
 ---
 
 # Choose the right PostgreSQL server option in Azure
 
-[!INCLUDE [applies-to-postgresql-single-server](../includes/applies-to-postgresql-single-server.md)]
+[!INCLUDE [applies-to-postgresql-flexible-server](../includes/applies-to-postgresql-flexible-server.md)]
 
 With Azure, your PostgreSQL Server workloads can run in a hosted virtual machine infrastructure as a service (IaaS) or as a hosted platform as a service (PaaS). PaaS has multiple deployment options, each with multiple service tiers. When you choose between IaaS and PaaS, you must decide if you want to manage your database, apply patches, and make backups, or if you want to delegate these operations to Azure.
 
-When making your decision, consider the following three options in PaaS or alternatively running on Azure VMs (IaaS)
-- [Azure Database for PostgreSQL Single Server](./overview-single-server.md)
+When making your decision, consider the following option in PaaS or alternatively running on Azure VMs (IaaS)
 - [Azure Database for PostgreSQL Flexible Server](../flexible-server/overview.md)
 
 **PostgreSQL on Azure VMs** option falls into the industry category of IaaS. With this service, you can run PostgreSQL Server inside a fully managed virtual machine on the Azure cloud platform. All recent versions and editions of PostgreSQL can be installed on an IaaS virtual machine. In the most significant difference from Azure Database for PostgreSQL, PostgreSQL on Azure VMs offers control over the database engine. However, this control comes at the cost of responsibility to manage the VMs and many database administration (DBA) tasks. These tasks include maintaining and patching database servers, database recovery, and high-availability design.
 
 The main differences between these options are listed in the following table:
 
-| **Attribute** | **Postgres on Azure VMs** | **PostgreSQL as PaaS** |
-| ----- | ----- | ----- |
-| **Availability SLA** |- [Virtual Machine SLA](https://azure.microsoft.com/support/legal/sla/virtual-machines) | - [Single Server and Flexible Server](https://azure.microsoft.com/support/legal/sla/postgresql)|
-| **OS and PostgreSQL patching** | - Customer managed | - Single Server – Automatic <br> - Flexible Server – Automatic with optional customer managed window |
-| **High availability** | - Customers architect, implement, test, and maintain high availability. Capabilities might include clustering, replication etc. | - Single Server:  built-in <br> - Flexible Server: built-in |
-| **Zone Redundancy** | - Azure VMs can be set up to run in different availability zones. For an on-premises solution, customers must create, manage, and maintain their own secondary data center.	| - Single Server: No <br> - Flexible Server: Yes |
-| **Hybrid Scenario** | - Customer managed |- Single Server: Read-replica <br> - Flexible Server: Not available during Preview |
-| **Backup and Restore** | - Customer Managed | - Single Server: built-in with user configuration for local and geo <br> - Flexible Server: built-in with user configuration on zone-redundant storage |
-| **Monitoring Database Operations** | - Customer Managed | - Single Server and Flexible Server: All offer customers the ability to set alerts on the database operation and act upon reaching thresholds. |
-| **Advanced Threat Protection** | - Customers must build this protection for themselves. |- Single Server: Yes <br> - Flexible Server: Not available during Preview |
-| **Disaster Recovery** | - Customer Managed | - Single Server: Geo redundant backup and geo read-replica <br> - Flexible Server: Not available during Preview |
-| **Intelligent Performance** | - Customer Managed | - Single Server: Yes <br> - Flexible Server: Not available during Preview |
+| **Attribute**                      | **Postgres on Azure VMs**                                                                                                                                                   | **PostgreSQL as PaaS**                                                                                                      |
+|------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------|
+| **Availability SLA**               | - [Virtual Machine SLA](https://azure.microsoft.com/support/legal/sla/virtual-machines)                                                                                     | - [Flexible Server](https://azure.microsoft.com/support/legal/sla/postgresql)                                               |
+| **OS and PostgreSQL patching**     | - Customer managed                                                                                                                                                          | - Flexible Server – Automatic with optional customer managed window                                                         |
+| **High availability**              | - Customers architect, implement, test, and maintain high availability. Capabilities might include clustering, replication etc.                                             | - Flexible Server: built-in                                                                                                 |
+| **Zone Redundancy**                | - Azure VMs can be set up to run in different availability zones. For an on-premises solution, customers must create, manage, and maintain their own secondary data center. | - Flexible Server: Yes                                                                                                      |
+| **Hybrid Scenario**                | - Customer managed                                                                                                                                                          | - Flexible Server: Not available during Preview                                                                             |
+| **Backup and Restore**             | - Customer Managed                                                                                                                                                          | - Flexible Server: built-in with user configuration on zone-redundant storage                                               |
+| **Monitoring Database Operations** | - Customer Managed                                                                                                                                                          | - Flexible Server: All offer customers the ability to set alerts on the database operation and act upon reaching thresholds |
+| **Advanced Threat Protection**     | - Customers must build this protection for themselves.                                                                                                                      | - Flexible Server: Not available during Preview                                                                             |
+| **Disaster Recovery**              | - Customer Managed                                                                                                                                                          | - Flexible Server: Not available during Preview                                                                             |
+| **Intelligent Performance**        | - Customer Managed                                                                                                                                                          | - Flexible Server: Not available during Preview                                                                             |
 
 ## Total cost of ownership (TCO)
 
@@ -47,7 +46,7 @@ Azure Database for PostgreSQL is currently available as a service in several tie
 
 With Azure Database for PostgreSQL, Microsoft automatically configures, patches, and upgrades the database software. These automated actions reduce your administration costs. Also, Azure Database for PostgreSQL has [automated backup-link]() capabilities. These capabilities help you achieve significant cost savings, especially when you have a large number of databases. In contrast, with PostgreSQL on Azure VMs you can choose and run any PostgreSQL version. However, you need to pay for the provisioned VM, storage cost associated with the data, backup, monitoring data and log storage and the costs for the specific PostgreSQL license type used (if any).
 
-Azure Database for PostgreSQL Single Server provides built-in high availability at the zonal-level (within an AZ) for any kind of node-level interruption while still maintaining the [SLA guarantee](https://azure.microsoft.com/support/legal/sla/postgresql/v1_2/) for the service. Flexible Server provides [uptime SLAs](https://azure.microsoft.com/support/legal/sla/postgresql/v1_2/) with and without zone-redundant configuration. However, for database high availability within VMs, you use the high availability options like [Streaming Replication](https://www.postgresql.org/docs/12/warm-standby.html#STREAMING-REPLICATION) that are available on a PostgreSQL database. Using a supported high availability option doesn't provide an additional SLA. But it does let you achieve greater than 99.99% database availability at additional cost and administrative overhead.
+Azure Database for PostgreSQL Flexible Server provides built-in high availability at the zonal-level (within an AZ) for any kind of node-level interruption while still maintaining the [SLA guarantee](https://azure.microsoft.com/support/legal/sla/postgresql/v1_2/) for the service. Flexible Server provides [uptime SLAs](https://azure.microsoft.com/support/legal/sla/postgresql/v1_2/) with and without zone-redundant configuration. However, for database high availability within VMs, you use the high availability options like [Streaming Replication](https://www.postgresql.org/docs/12/warm-standby.html#STREAMING-REPLICATION) that are available on a PostgreSQL database. Using a supported high availability option doesn't provide an additional SLA. But it does let you achieve greater than 99.99% database availability at additional cost and administrative overhead.
 
 For more information on pricing, see the following articles:
 - [Azure Database for PostgreSQL pricing](https://azure.microsoft.com/pricing/details/postgresql/server/)