mysql

Author: Alicja Kucharczyk

articles/postgresql/flexible-server/concepts-firewall-rules.md

@@ -19,22 +19,22 @@ With public access, the Azure Database for PostgreSQL flexible server instance i
 
 You can create firewall rules by using the Azure portal or by using Azure CLI commands. You must be the subscription owner or a subscription contributor.
 
-Server-level firewall rules apply to all databases on the same Azure Database for MySQL flexible server instance. The rules don't affect access to the Azure portal website.
+Server-level firewall rules apply to all databases on the same Azure Database for PostgreSQL flexible server instance. The rules don't affect access to the Azure portal website.
 
-The following diagram shows how connection attempts from the internet and Azure must pass through the firewall before they can reach Azure Database for MySQL flexible server databases:
+The following diagram shows how connection attempts from the internet and Azure must pass through the firewall before they can reach Azure Database for PostgreSQL flexible server databases:
 
 :::image type="content" source="../media/concepts-firewall-rules/1-firewall-concept.png" alt-text="Diagram that shows an overview of how the firewall works.":::
 
 ## Connect from the internet
 If the source IP address of the request is within one of the ranges specified in the server-level firewall rules, the connection is granted. Otherwise, it's rejected. 
 
-For example, if your application connects with a Java Database Connectivity (JDBC) driver for Azure Database for MySQL flexible server, you might encounter this error because the firewall is blocking the connection:
+For example, if your application connects with a Java Database Connectivity (JDBC) driver for Azure Database for PostgreSQL flexible server, you might encounter this error because the firewall is blocking the connection:
 
 > java.util.concurrent.ExecutionException: java.lang.RuntimeException:
 > org.postgresql.util.PSQLException: FATAL: no pg\_hba.conf entry for host "123.45.67.890", user "adminuser", database "postgresql", SSL
 
 > [!NOTE]
-> To access Azure Database for MySQL flexible server from your local computer, ensure that the firewall on your network and local computer allow outgoing communication on TCP port 5432.
+> To access Azure Database for PostgreSQL flexible server from your local computer, ensure that the firewall on your network and local computer allow outgoing communication on TCP port 5432.
 
 ## Connect from Azure
 We recommend that you find the outgoing IP address of any application or service and explicitly allow access to those individual IP addresses or ranges. For example, you can find the outgoing IP address of an Azure App Service app, or use a public IP address that's tied to a virtual machine. 
@@ -52,22 +52,22 @@ If a fixed outgoing IP address isn't available for your Azure service, consider
 ## Programmatically manage firewall rules
 In addition to using the Azure portal, you can manage firewall rules programmatically by using the Azure CLI. 
 
-From the Azure CLI, a firewall rule setting with a starting and ending address equal to 0.0.0.0 does the equivalent of the **Allow public access from any Azure service within Azure to this server** option in the portal. If firewall rules reject the connection attempt, the app won't reach the Azure Database for MySQL flexible server instance.
+From the Azure CLI, a firewall rule setting with a starting and ending address equal to 0.0.0.0 does the equivalent of the **Allow public access from any Azure service within Azure to this server** option in the portal. If firewall rules reject the connection attempt, the app won't reach the Azure Database for PostgreSQL flexible server instance.
 
 ## Troubleshoot firewall problems
-Consider the following possibilities when access to an Azure Database for MySQL flexible server instance doesn't behave as you expect:
+Consider the following possibilities when access to an Azure Database for PostgreSQL flexible server instance doesn't behave as you expect:
 
-* **Changes to the allowlist haven't taken effect yet**: Changes to the firewall configuration of an Azure Database for MySQL flexible server instance might take up to five minutes.
+* **Changes to the allowlist haven't taken effect yet**: Changes to the firewall configuration of an Azure Database for PostgreSQL flexible server instance might take up to five minutes.
 
-* **The sign-in isn't authorized, or an incorrect password was used**: If a sign-in doesn't have permissions on the Azure Database for MySQL flexible server instance or the password is incorrect, the connection to the server is denied. Creating a firewall setting only provides clients with an opportunity to try connecting to your server. Each client must still provide the necessary security credentials.
+* **The sign-in isn't authorized, or an incorrect password was used**: If a sign-in doesn't have permissions on the Azure Database for PostgreSQL flexible server instance or the password is incorrect, the connection to the server is denied. Creating a firewall setting only provides clients with an opportunity to try connecting to your server. Each client must still provide the necessary security credentials.
 
   For example, the following error might appear if authentication fails for a JDBC client:
 
   > java.util.concurrent.ExecutionException: java.lang.RuntimeException: org.postgresql.util.PSQLException: FATAL: password authentication failed for user "yourusername"
 
 * **The firewall isn't allowing dynamic IP addresses**: If you have an internet connection with dynamic IP addressing and you're having trouble getting through the firewall, try one of the following solutions:
 
-  * Ask your internet service provider (ISP) for the IP address range assigned to your client computers that access the Azure Database for MySQL flexible server instance. Then add the IP address range as a firewall rule.
+  * Ask your internet service provider (ISP) for the IP address range assigned to your client computers that access the Azure Database for PostgreSQL flexible server instance. Then add the IP address range as a firewall rule.
 
   * Get static IP addresses instead for your client computers, and then add the static IP addresses as a firewall rule.
 
@@ -76,5 +76,5 @@ Consider the following possibilities when access to an Azure Database for MySQL
 
 ## Next steps
 
-* [Create and manage Azure Database for MySQL flexible server firewall rules by using the Azure portal](how-to-manage-firewall-portal.md)
-* [Create and manage Azure Database for MySQL flexible server firewall rules by using the Azure CLI](how-to-manage-firewall-cli.md)
+* [Create and manage Azure Database for PostgreSQL flexible server firewall rules by using the Azure portal](how-to-manage-firewall-portal.md)
+* [Create and manage Azure Database for PostgreSQL flexible server firewall rules by using the Azure CLI](how-to-manage-firewall-cli.md)

articles/postgresql/flexible-server/concepts-geo-disaster-recovery.md

@@ -17,7 +17,7 @@ ms.date: 10/23/2023
 
 If there's a region-wide disaster, Azure can provide protection from regional or large geography disasters with disaster recovery by making use of another region. For more information on Azure disaster recovery architecture, see [Azure to Azure disaster recovery architecture](../../site-recovery/azure-to-azure-architecture.md).
 
-Azure Database for MySQL flexible server provides features that protect data and mitigates downtime for your mission-critical databases during planned and unplanned downtime events. Built on top of the Azure infrastructure that offers robust resiliency and availability, Azure Database for MySQL flexible server offers business continuity features that provide fault-protection, address recovery time requirements, and reduce data loss exposure. As you architect your applications, you should consider the downtime tolerance - the recovery time objective (RTO), and data loss exposure - the recovery point objective (RPO). For example, your business-critical database requires stricter uptime than a test database.
+Azure Database for PostgreSQL flexible server provides features that protect data and mitigates downtime for your mission-critical databases during planned and unplanned downtime events. Built on top of the Azure infrastructure that offers robust resiliency and availability, Azure Database for PostgreSQL flexible server offers business continuity features that provide fault-protection, address recovery time requirements, and reduce data loss exposure. As you architect your applications, you should consider the downtime tolerance - the recovery time objective (RTO), and data loss exposure - the recovery point objective (RPO). For example, your business-critical database requires stricter uptime than a test database.
 
 ## Compare geo-replication with geo-redundant backup storage
 Both geo-replication with read replicas and geo-backup are solutions for geo-disaster recovery. However, they differ in the details of their offerings. To choose the right solution for your system, it's important to understand and compare their features.
@@ -43,7 +43,7 @@ For more information on geo-redundant backup and restore, see [geo-redundant bac
 
 ## Read replicas
 
-Cross region read replicas can be deployed to protect your databases from region-level failures. Read replicas are updated asynchronously using Azure Database for MySQL flexible server's physical replication technology, and can lag the primary. Read replicas are supported in general purpose and memory optimized compute tiers.
+Cross region read replicas can be deployed to protect your databases from region-level failures. Read replicas are updated asynchronously using Azure Database for PostgreSQL flexible server's physical replication technology, and can lag the primary. Read replicas are supported in general purpose and memory optimized compute tiers.
 
 For more information on read replica features and considerations, see [Read replicas](/azure/postgresql/flexible-server/concepts-read-replicas).
 
@@ -58,7 +58,7 @@ For more information on unplanned downtime mitigation and recovery after regiona
 ## Next steps
 
 > [!div class="nextstepaction"]
-> [Azure Database for MySQL flexible server documentation](/azure/postgresql/)
+> [Azure Database for PostgreSQL flexible server documentation](/azure/postgresql/)
 
 > [!div class="nextstepaction"]
 > [Reliability in Azure](../../reliability/availability-zones-overview.md)

articles/postgresql/flexible-server/concepts-high-availability.md

@@ -13,7 +13,7 @@ ms.date: 7/19/2023
 
 [!INCLUDE [applies-to-postgresql-flexible-server](../includes/applies-to-postgresql-flexible-server.md)]
 
-Azure Database for PostgreSQL flexible server offers high availability configurations with automatic failover capabilities. The high availability solution is designed to ensure that committed data is never lost because of failures and that the database won't be a single point of failure in your architecture. When high availability is configured, Azure Database for MySQL flexible server automatically provisions and manages a standby. Write-ahead-logs (WAL) is streamed to the replica in synchronous mode using PostgreSQL streaming replication. There are two high availability architectural models: 
+Azure Database for PostgreSQL flexible server offers high availability configurations with automatic failover capabilities. The high availability solution is designed to ensure that committed data is never lost because of failures and that the database won't be a single point of failure in your architecture. When high availability is configured, Azure Database for PostgreSQL - Flexible Server automatically provisions and manages a standby. Write-ahead-logs (WAL) is streamed to the replica in synchronous mode using PostgreSQL streaming replication. There are two high availability architectural models: 
 
 * **Zone-redundant HA**: This option provides a complete isolation and redundancy of infrastructure across multiple availability zones within a region. It provides the highest level of availability, but it requires you to configure application redundancy across availability zones. Zone-redundant HA is preferred when you want protection from availability zone failures. However, one should account for added latency for cross-AZ synchronous writes. This latency is more pronounced for applications with short duration transactions.  Zone-redundant HA is available in a [subset of Azure regions](./overview.md#azure-regions) where the region supports multiple [availability zones](../../availability-zones/az-overview.md). Uptime [SLA of 99.99%](https://azure.microsoft.com/support/legal/sla/postgresql) is offered in this configuration.
 * **Same-zone HA**: This option provides for infrastructure redundancy with lower network latency because the primary and standby servers will be in the same availability zone. It provides high availability without the need to configure application redundancy across zones. Same-zone HA is preferred when you want to achieve the highest level of availability within a single availability zone. This option lowers the latency impact but makes your application vulnerable to zone failures.  Same-zone HA is available in all [Azure regions](./overview.md#azure-regions) where you can deploy Azure Database for PostgreSQL flexible server.  Uptime [SLA of 99.95%](https://azure.microsoft.com/support/legal/sla/postgresql) offered in this configuration. 

articles/postgresql/flexible-server/connect-csharp.md

@@ -334,7 +334,7 @@ az group delete \
 ## Next steps
 
 > [!div class="nextstepaction"]
-> [Manage Azure Database for MySQL server using Portal](./how-to-manage-server-portal.md)<br/>
+> [Manage Azure Database for PostgreSQL server using Portal](./how-to-manage-server-portal.md)<br/>
 
 > [!div class="nextstepaction"]
-> [Manage Azure Database for MySQL server using CLI](./how-to-manage-server-cli.md)
+> [Manage Azure Database for PostgreSQL server using CLI](./how-to-manage-server-cli.md)