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/postgresql/flexible-server/overview.md
+9-17Lines changed: 9 additions & 17 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -14,13 +14,13 @@ ms.topic: overview
14
14
15
15
This article provides an overview of Azure Database for PostgreSQL, helping you get acquainted with its key features and core concepts.
16
16
17
-
Azure Database for PostgreSQL is a fully managed database service designed to give more granular control and flexibility over database management functions and configuration settings. The service generally provides more flexibility and server configuration customizations based on your requirements. The architecture lets you collocate the database engine with the client tier for lower latency and choose high availability within a single availability zone and across multiple availability zones. Azure Database for PostgreSQL flexible server instances also provides better cost optimization controls with the ability to stop and start your server and a burstable compute tier that's ideal for workloads that don't need full compute capacity continuously. The service supports various major community versions of PostgreSQL. For details on the specific versions supported, see [Supported versions of PostgreSQL in Azure Database for PostgreSQL](concepts-supported-versions.md). The service is available in various [Azure regions](https://azure.microsoft.com/global-infrastructure/services/).
17
+
Azure Database for PostgreSQL is a fully managed database service designed to give you granular control and flexibility over database management functions and configuration settings. The service provides flexibility and server configuration customizations based on your requirements. The architecture lets you collocate the database engine with the client tier for lower latency and choose high availability within a single availability zone and across multiple availability zones. Azure Database for PostgreSQL flexible server instances also provides cost optimization controls with the ability to stop and start your server and a burstable compute tier that's ideal for workloads that don't need full compute capacity continuously. The service supports various major community versions of PostgreSQL. For details on the specific versions supported, see [Supported versions of PostgreSQL in Azure Database for PostgreSQL](concepts-supported-versions.md). The service is available in various [Azure regions](https://azure.microsoft.com/global-infrastructure/services/).
18
18
19
19
:::image type="content" source="./media/overview/overview-flexible-server.png" alt-text="Diagram of Azure Database for PostgreSQL - Overview." lightbox="./media/overview/overview-flexible-server.png":::
20
20
21
-
Azure Database for PostgreSQL flexible server instances are best suited for:
21
+
Azure Database for PostgreSQL flexible server instances is best suited for:
22
22
23
-
- Application developments requiring better control and customizations.
23
+
- Application developments requiring control and customizations.
24
24
- Zone redundant high availability.
25
25
- Managed maintenance windows.
26
26
@@ -32,7 +32,7 @@ If you configure zone redundant high availability, the service provisions and ma
32
32
33
33
:::image type="content" source="~/reusable-content/ce-skilling/azure/media/postgresql/concepts-zone-redundant-high-availability-architecture.png" alt-text="Diagram of Zone redundant high availability." lightbox="~/reusable-content/ce-skilling/azure/media/postgresql/concepts-zone-redundant-high-availability-architecture.png":::
34
34
35
-
See [High availability]/azure/reliability/reliability-postgresql-flexible-server for more details.
35
+
See [High availability](/azure/reliability/reliability-postgresql-flexible-server) for more details.
36
36
37
37
## Automated patching with a managed maintenance window
38
38
@@ -46,15 +46,15 @@ Azure Database for PostgreSQL automatically creates server backups and stores th
46
46
47
47
Azure Database for PostgreSQL is available in three compute tiers: Burstable, General Purpose, and Memory Optimized. The Burstable tier is best for low-cost development and low concurrency workloads without continuous compute capacity. The General Purpose and Memory Optimized tiers are better for production workloads that require high concurrency, scale, and predictable performance. You can build your first application on a small database for a few dollars a month, then seamlessly adjust the scale to meet the needs of your solution.
48
48
49
-
## Stop/start server to lower TCO
49
+
## Stop and start server to lower TCO
50
50
51
51
Azure Database for PostgreSQL allows you to stop and start the server on demand to lower your TCO. The compute tier billing stops immediately when you stop the server. This feature can provide significant cost savings during development, testing, and time-bound predictable production workloads. The server remains stopped for seven days unless you restart it sooner.
52
52
53
53
## Enterprise-grade security
54
54
55
55
Azure Database for PostgreSQL uses the FIPS 140-2 validated cryptographic module for storage encryption of data at rest. The service encrypts data, including backups and temporary files created while running queries. It uses the AES 256-bit cipher included in Azure storage encryption, and the keys can be system-managed (default). Azure Database for PostgreSQL encrypts data in motion with default transport layer security (SSL/TLS) enforced by default. The service enforces and supports TLS version 1.2 and later.
56
56
57
-
Azure Database for PostgreSQL flexible server instances allows full private access to the servers using Azure virtual network. Servers in the Azure virtual network can only be reached and connected through private IP addresses. With virtual network integration, public access is denied, and servers can't be reached using public endpoints.
57
+
Azure Database for PostgreSQL flexible server instances allows full private access to the servers by using Azure virtual network. Servers in the Azure virtual network can only be reached and connected through private IP addresses. With virtual network integration, public access is denied, and servers can't be reached by using public endpoints.
58
58
59
59
## Monitor and alerting
60
60
@@ -68,25 +68,17 @@ An Azure Database for PostgreSQL flexible server instance has a [built-in PgBoun
68
68
69
69
One advantage of running your workload in Azure is global reach. Azure Database for PostgreSQL is currently available in the following Azure regions:
$ New zone-redundant high availability deployments are temporarily blocked in these regions. Already provisioned HA servers are fully supported.
74
-
75
-
$$ New server deployments are temporarily blocked in these regions. Already provisioned servers are fully supported.
76
-
77
-
** Zone-redundant high availability can now be deployed when you provision new servers in these regions. Any existing servers deployed in AZ with *no preference* (check this on the Azure portal) before the region started to support AZ, even when you enable zone-redundant HA, the standby is provisioned in the same AZ (same-zone HA) as the primary server. To enable zone-redundant high availability in such cases, read these [special considerations](how-to-configure-high-availability.md#special-considerations).
78
-
79
-
(*) Certain regions are access-restricted to support specific customer scenarios, such as in-country/region disaster recovery. You can access these regions only upon request by creating a new support request.
71
+
See the [regions table](includes/regions-table.md) for the list of available Azure regions.
80
72
81
73
> [!NOTE]
82
-
> If your application requires zone-redundant HA and it's unavailable in your preferred Azure region, consider using other regions within the same geography where zone-redundant HA is available, such as US East for US East 2, Central US for North Central US, and so on.
74
+
> If your application requires zone-redundant high availabilityA and it's unavailable in your preferred Azure region, consider using other regions within the same geography where zone-redundant HA is available, such as US East for US East 2, Central US for North Central US, and so on.
83
75
84
76
## Migration
85
77
86
78
Azure Database for PostgreSQL runs the community version of PostgreSQL. This version provides full application compatibility and requires minimal refactoring to migrate an existing application developed on the PostgreSQL engine to Azure Database for PostgreSQL.
87
79
88
80
-**Azure Database Migration Service** – For seamless and simplified migrations to Azure Database for PostgreSQL with minimal downtime, use Azure Database Migration Service. Visit [What is the migration service in Azure Database for PostgreSQL?](../migrate/migration-service/overview-migration-service-postgresql.md)
89
-
- **Dump and Restore** – For offline migrations where you can afford some downtime, dump and restore using community tools like pg_dump and pg_restore provides the fastest way to migrate. See [Migrate using dump and restore](../howto-migrate-using-dump-and-restore.md) for details.
81
+
-**Dump and Restore** – For offline migrations where you can afford some downtime, dump, and restore using community tools like pg_dump and pg_restore provides the fastest way to migrate. See [Migrate using dump and restore](../howto-migrate-using-dump-and-restore.md) for details.
0 commit comments