Merge pull request #108178 from ajlam/master

GitHubber17 · web-flow · commit 1c7bf0419716 · 2020-03-18T12:57:48.000-07:00
Refresh MariaDB docs
diff --git a/articles/mariadb/concept-reserved-pricing.md b/articles/mariadb/concept-reserved-pricing.md
@@ -5,7 +5,7 @@ author: kummanish
 ms.author: manishku
 ms.service: mariadb
 ms.topic: conceptual
-ms.date: 12/02/2019
+ms.date: 3/18/2020
 ---
 
 # Prepay for Azure Database for MariaDB compute resources with reserved capacity
@@ -46,8 +46,8 @@ The following table describes required fields.
 | Field | Description |
 | :------------ | :------- |
 | Subscription   | The subscription used to pay for the Azure Database for MariaDB reserved capacity reservation. The payment method on the subscription is charged the upfront costs for the Azure Database for MariaDB reserved capacity reservation. The subscription type must be an enterprise agreement (offer numbers: MS-AZR-0017P or MS-AZR-0148P) or an individual agreement with pay-as-you-go pricing (offer numbers: MS-AZR-0003P or MS-AZR-0023P). For an enterprise subscription, the charges are deducted from the enrollment's monetary commitment balance or charged as overage. For an individual subscription with pay-as-you-go pricing, the charges are billed to the credit card or invoice payment method on the subscription.
-| Scope | The vCore reservation’s scope can cover one subscription or multiple subscriptions (shared scope). If you select: </br></br> **Shared**, the vCore reservation discount is applied to Azure Database for MariaDB servers running in any subscriptions within your billing context. For enterprise customers, the shared scope is the enrollment and includes all subscriptions within the enrollment. For Pay-As-You-Go customers, the shared scope is all Pay-As-You-Go subscriptions created by the account administrator.</br></br> **Single subscription**, the vCore reservation discount is applied to Azure Database for MariaDB servers in this subscription. </br></br> **Single resource group**, the reservation discount is applied to Azure Database for MariaDB servers in the selected subscription and the selected resource group within that subscription.
-| Region | The Azure region that’s covered by the Azure Database for MariaDB reserved capacity reservation.
+| Scope | The vCore reservation's scope can cover one subscription or multiple subscriptions (shared scope). If you select: </br></br> **Shared**, the vCore reservation discount is applied to Azure Database for MariaDB servers running in any subscriptions within your billing context. For enterprise customers, the shared scope is the enrollment and includes all subscriptions within the enrollment. For Pay-As-You-Go customers, the shared scope is all Pay-As-You-Go subscriptions created by the account administrator.</br></br> **Single subscription**, the vCore reservation discount is applied to Azure Database for MariaDB servers in this subscription. </br></br> **Single resource group**, the reservation discount is applied to Azure Database for MariaDB servers in the selected subscription and the selected resource group within that subscription.
+| Region | The Azure region that's covered by the Azure Database for MariaDB reserved capacity reservation.
 | Deployment Type | The Azure Database for MariaDB resource type that you want to buy the reservation for.
 | Performance Tier | The service tier for the Azure Database for MariaDB servers.
 | Term | One year
diff --git a/articles/mariadb/concepts-audit-logs.md b/articles/mariadb/concepts-audit-logs.md
@@ -5,7 +5,7 @@ author: ajlam
 ms.author: andrela
 ms.service: mariadb
 ms.topic: conceptual
-ms.date: 12/09/2019
+ms.date: 3/18/2020
 ---
 
 # Audit Logs in Azure Database for MariaDB
diff --git a/articles/mariadb/concepts-backup.md b/articles/mariadb/concepts-backup.md
@@ -5,7 +5,7 @@ author: ajlam
 ms.author: andrela
 ms.service: mariadb
 ms.topic: conceptual
-ms.date: 02/25/2020
+ms.date: 3/18/2020
 ---
 
 # Backup and restore in Azure Database for MariaDB
diff --git a/articles/mariadb/concepts-business-continuity.md b/articles/mariadb/concepts-business-continuity.md
@@ -5,7 +5,7 @@ author: ajlam
 ms.author: andrela
 ms.service: mariadb
 ms.topic: conceptual
-ms.date: 12/02/2019
+ms.date: 3/18/2020
 ---
 
 # Understand business continuity in Azure Database for MariaDB
@@ -28,7 +28,7 @@ The following table compares the ERT and RPO for the available features:
 
 ## Recover a server after a user or application error
 
-You can use the service’s backups to recover a server from various disruptive events. A user may accidentally delete some data, inadvertently drop an important table, or even drop an entire database. An application might accidentally overwrite good data with bad data due to an application defect, and so on.
+You can use the service's backups to recover a server from various disruptive events. A user may accidentally delete some data, inadvertently drop an important table, or even drop an entire database. An application might accidentally overwrite good data with bad data due to an application defect, and so on.
 
 You can perform a point-in-time-restore to create a copy of your server to a known good point in time. This point in time must be within the backup retention period you have configured for your server. After the data is restored to the new server, you can either replace the original server with the newly restored server or copy the needed data from the restored server into the original server.
 
diff --git a/articles/mariadb/concepts-compatibility.md b/articles/mariadb/concepts-compatibility.md
@@ -5,7 +5,7 @@ author: ajlam
 ms.author: andrela
 ms.service: mariadb
 ms.topic: conceptual
-ms.date: 12/02/2019
+ms.date: 3/18/2020
 ---
 # MariaDB drivers and management tools compatible with Azure Database for MariaDB
 
diff --git a/articles/mariadb/concepts-connectivity-architecture.md b/articles/mariadb/concepts-connectivity-architecture.md
@@ -5,7 +5,7 @@ author: kummanish
 ms.author: manishku
 ms.service: mariadb
 ms.topic: conceptual
-ms.date: 12/02/2019
+ms.date: 3/18/2020
 ---
 
 # Connectivity architecture in Azure Database for MariaDB
@@ -25,43 +25,43 @@ The following table lists the primary and secondary IPs of the Azure Database fo
 
 | **Region Name** | **Gateway IP Addresses** |
 |:----------------|:-------------|
-| Australia Central| 20.36.105.0	 |
-| Australia Central2	 | 20.36.113.0	 |
-| Australia East | 13.75.149.87, 40.79.161.1	 |
-| Australia South East |191.239.192.109, 13.73.109.251	 |
-| Brazil South | 104.41.11.5, 191.233.201.8, 191.233.200.16	 |
-| Canada Central |40.85.224.249	 |
-| Canada East | 40.86.226.166	 |
-| Central US | 23.99.160.139, 13.67.215.62	 |
-| China East 2 | 40.73.82.1	 |
-| China North 2 | 40.73.50.0	 |
-| East Asia | 191.234.2.139, 52.175.33.150, 13.75.33.20, 13.75.33.21	 |
-| East US | 40.121.158.30, 191.238.6.43	 |
-| East US 2 |40.79.84.180, 191.239.224.107, 52.177.185.181	 |
-| France Central | 40.79.137.0, 40.79.129.1	 |
-| Germany Central | 51.4.144.100	 |
-| Germany North East | 51.5.144.179	 |
-| India Central | 104.211.96.159	 |
-| India South | 104.211.224.146	 |
-| India West | 104.211.160.80	 |
-| Japan East | 13.78.61.196, 191.237.240.43	 |
-| Japan West | 104.214.148.156, 191.238.68.11, 40.74.96.6, 40.74.96.7	 |
-| Korea Central | 52.231.32.42	 |
-| Korea South | 52.231.200.86	 |
-| North Central US | 23.96.178.199, 23.98.55.75, 52.162.104.35, 52.162.104.36	 |
-| North Europe | 40.113.93.91, 191.235.193.75	 |
-| South Africa North  | 102.133.152.0	 |
-| South Africa West	| 102.133.24.0	 |
-| South Central US |13.66.62.124, 23.98.162.75, 20.45.120.0, 104.214.16.39	 |
-| South East Asia | 104.43.15.0, 23.100.117.95, 40.78.233.2, 23.98.80.12	 |
-| UAE Central | 20.37.72.64	 |
-| UAE North | 65.52.248.0	 |
-| UK South | 51.140.184.11	 |
-| UK West | 51.141.8.11	 |
-| West Central US | 13.78.145.25	 |
-| West Europe | 40.68.37.158, 191.237.232.75	 |
-| West US | 104.42.238.205, 23.99.34.75	 |
-| West US 2 | 13.66.226.202	 |
+| Australia Central| 20.36.105.0     |
+| Australia Central2     | 20.36.113.0     |
+| Australia East | 13.75.149.87, 40.79.161.1     |
+| Australia South East |191.239.192.109, 13.73.109.251     |
+| Brazil South | 104.41.11.5, 191.233.201.8, 191.233.200.16     |
+| Canada Central |40.85.224.249     |
+| Canada East | 40.86.226.166     |
+| Central US | 23.99.160.139, 13.67.215.62     |
+| China East 2 | 40.73.82.1     |
+| China North 2 | 40.73.50.0     |
+| East Asia | 191.234.2.139, 52.175.33.150, 13.75.33.20, 13.75.33.21     |
+| East US | 40.121.158.30, 191.238.6.43     |
+| East US 2 |40.79.84.180, 191.239.224.107, 52.177.185.181     |
+| France Central | 40.79.137.0, 40.79.129.1     |
+| Germany Central | 51.4.144.100     |
+| Germany North East | 51.5.144.179     |
+| India Central | 104.211.96.159     |
+| India South | 104.211.224.146     |
+| India West | 104.211.160.80     |
+| Japan East | 13.78.61.196, 191.237.240.43     |
+| Japan West | 104.214.148.156, 191.238.68.11, 40.74.96.6, 40.74.96.7     |
+| Korea Central | 52.231.32.42     |
+| Korea South | 52.231.200.86     |
+| North Central US | 23.96.178.199, 23.98.55.75, 52.162.104.35, 52.162.104.36     |
+| North Europe | 40.113.93.91, 191.235.193.75     |
+| South Africa North  | 102.133.152.0     |
+| South Africa West    | 102.133.24.0     |
+| South Central US |13.66.62.124, 23.98.162.75, 20.45.120.0, 104.214.16.39     |
+| South East Asia | 104.43.15.0, 23.100.117.95, 40.78.233.2, 23.98.80.12     |
+| UAE Central | 20.37.72.64     |
+| UAE North | 65.52.248.0     |
+| UK South | 51.140.184.11     |
+| UK West | 51.141.8.11     |
+| West Central US | 13.78.145.25     |
+| West Europe | 40.68.37.158, 191.237.232.75     |
+| West US | 104.42.238.205, 23.99.34.75     |
+| West US 2 | 13.66.226.202     |
 ||||
 
 ## Next steps
diff --git a/articles/mariadb/concepts-connectivity.md b/articles/mariadb/concepts-connectivity.md
@@ -6,7 +6,7 @@ author: jan-eng
 ms.author: janeng
 ms.service: mariadb
 ms.topic: conceptual
-ms.date: 12/02/2019
+ms.date: 3/18/2020
 ---
 
 # Handling of transient connectivity errors for Azure Database for MariaDB
@@ -31,7 +31,7 @@ The first and second case are fairly straight forward to handle. Try to open the
 * For each following retry, the increase the wait exponentially, up to 60 seconds.
 * Set a max number of retries at which point your application considers the operation failed.
 
-When a connection with an active transaction fails, it is more difficult to handle the recovery correctly. There are two cases: If the transaction was read-only in nature, it is safe to reopen the connection and to retry the transaction. If however if the transaction was also writing to the database, you must determine if the transaction was rolled back, or if it succeeded before the transient error happened. In that case, you might just not have received the commit acknowledgement from the database server.
+When a connection with an active transaction fails, it is more difficult to handle the recovery correctly. There are two cases: If the transaction was read-only in nature, it is safe to reopen the connection and to retry the transaction. If however if the transaction was also writing to the database, you must determine if the transaction was rolled back, or if it succeeded before the transient error happened. In that case, you might not have received the commit acknowledgment from the database server.
 
 One way of doing this, is to generate a unique ID on the client that is used for all the retries. You pass this unique ID as part of the transaction to the server and to store it in a column with a unique constraint. This way you can safely retry the transaction. It will succeed if the previous transaction was rolled back and the client generated unique ID does not yet exist in the system. It will fail indicating a duplicate key violation if the unique ID was previously stored because the previous transaction completed successfully.
 
diff --git a/articles/mariadb/concepts-data-access-and-security-threat-protection.md b/articles/mariadb/concepts-data-access-and-security-threat-protection.md
@@ -5,7 +5,7 @@ author: ajlam
 ms.author: andrela
 ms.service: mariadb
 ms.topic: conceptual
-ms.date: 12/02/2019
+ms.date: 3/18/2020
 ---
 # Azure Database for MariaDB Advanced Threat Protection
 
diff --git a/articles/mariadb/concepts-data-access-security-vnet.md b/articles/mariadb/concepts-data-access-security-vnet.md
@@ -5,7 +5,7 @@ author: ajlam
 ms.author: andrela
 ms.service: mariadb
 ms.topic: conceptual
-ms.date: 12/02/2019
+ms.date: 3/18/2020
 ---
 # Use Virtual Network service endpoints and rules for Azure Database for MariaDB
 
diff --git a/articles/mariadb/concepts-data-in-replication.md b/articles/mariadb/concepts-data-in-replication.md
@@ -5,7 +5,7 @@ author: ajlam
 ms.author: andrela
 ms.service: mariadb
 ms.topic: conceptual
-ms.date: 12/02/2019
+ms.date: 3/18/2020
 ---
 
 # Replicate data into Azure Database for MariaDB
diff --git a/articles/mariadb/concepts-firewall-rules.md b/articles/mariadb/concepts-firewall-rules.md
@@ -5,7 +5,7 @@ author: ajlam
 ms.author: andrela
 ms.service: mariadb
 ms.topic: conceptual
-ms.date: 01/15/2020
+ms.date: 3/18/2020
 ---
 
 # Azure Database for MariaDB server firewall rules
diff --git a/articles/mariadb/concepts-high-availability.md b/articles/mariadb/concepts-high-availability.md
@@ -5,7 +5,7 @@ author: ajlam
 ms.author: andrela
 ms.service: mariadb
 ms.topic: conceptual
-ms.date: 12/02/2019
+ms.date: 3/18/2020
 ---
 # High availability concepts in Azure Database for MariaDB
 The Azure Database for MariaDB service provides a guaranteed high level of availability. The financially backed service level agreement (SLA) is 99.99% upon general availability. There is virtually no application down time when using this service.
diff --git a/articles/mariadb/concepts-monitoring.md b/articles/mariadb/concepts-monitoring.md
@@ -5,7 +5,7 @@ author: ajlam
 ms.author: andrela
 ms.service: mariadb
 ms.topic: conceptual
-ms.date: 12/02/2019
+ms.date: 3/18/2020
 ---
 # Monitoring in Azure Database for MariaDB
 Monitoring data about your servers helps you troubleshoot and optimize for your workload. Azure Database for MariaDB provides various metrics that give insight into the behavior of your server.
diff --git a/articles/mariadb/concepts-performance-recommendations.md b/articles/mariadb/concepts-performance-recommendations.md
@@ -5,7 +5,7 @@ author: ajlam
 ms.author: andrela
 ms.service: mariadb
 ms.topic: conceptual
-ms.date: 12/02/2019
+ms.date: 3/18/2020
 ---
 # Performance Recommendations in Azure Database for MariaDB
 
diff --git a/articles/mariadb/concepts-pricing-tiers.md b/articles/mariadb/concepts-pricing-tiers.md
@@ -5,7 +5,7 @@ author: jan-eng
 ms.author: janeng
 ms.service: mariadb
 ms.topic: conceptual
-ms.date: 02/25/2020
+ms.date: 3/18/2020
 ---
 
 # Azure Database for MariaDB pricing tiers
diff --git a/articles/mariadb/concepts-query-performance-insight.md b/articles/mariadb/concepts-query-performance-insight.md
@@ -5,7 +5,7 @@ author: ajlam
 ms.author: andrela
 ms.service: mariadb
 ms.topic: conceptual
-ms.date: 12/02/2019
+ms.date: 3/18/2020
 ---
 # Query Performance Insight in Azure Database for MariaDB
 
diff --git a/articles/mariadb/concepts-query-store.md b/articles/mariadb/concepts-query-store.md
@@ -5,7 +5,7 @@ author: ajlam
 ms.author: andrela
 ms.service: mariadb
 ms.topic: conceptual
-ms.date: 12/02/2019
+ms.date: 3/18/2020
 ---
 # Monitor Azure Database for MariaDB performance with Query Store
 
diff --git a/articles/mariadb/concepts-read-replicas.md b/articles/mariadb/concepts-read-replicas.md
@@ -5,7 +5,7 @@ author: ajlam
 ms.author: andrela
 ms.service: mariadb
 ms.topic: conceptual
-ms.date: 01/16/2020
+ms.date: 3/18/2020
 ---
 
 # Read replicas in Azure Database for MariaDB
@@ -26,7 +26,6 @@ Because replicas are read-only, they don't directly reduce write-capacity burden
 
 The read replica feature uses asynchronous replication. The feature isn't meant for synchronous replication scenarios. There will be a measurable delay between the master and the replica. The data on the replica eventually becomes consistent with the data on the master. Use this feature for workloads that can accommodate this delay.
 
-
 ## Cross-region replication
 You can create a read replica in a different region from your master server. Cross-region replication can be helpful for scenarios like disaster recovery planning or bringing data closer to your users.
 
@@ -44,7 +43,6 @@ Australia East, Australia Southeast, Central US, East Asia, East US, East US 2,
 
 *West US 2 is temporarily unavailable as a cross region replica location.
 
-
 ### Paired regions
 In addition to the universal replica regions, you can create a read replica in the Azure paired region of your master server. If you don't know your region's pair, you can learn more from the [Azure Paired Regions article](../best-practices-availability-paired-regions.md).
 
@@ -53,11 +51,10 @@ If you are using cross-region replicas for disaster recovery planning, we recomm
 However, there are limitations to consider: 
 
 * Regional availability: Azure Database for MariaDB is available in West US 2, France Central, UAE North, and Germany Central. However, their paired regions are not available.
-	
+    
 * Uni-directional pairs: Some Azure regions are paired in one direction only. These regions include West India, Brazil South, and US Gov Virginia. 
    This means that a master server in West India can create a replica in South India. However, a master server in South India cannot create a replica in West India. This is because West India's secondary region is South India, but South India's secondary region is not West India.
 
-
 ## Create a replica
 
 If a master server has no existing replica servers, the master will first restart to prepare itself for replication.
@@ -89,7 +86,7 @@ Azure Database for MariaDB provides the **Replication lag in seconds** metric in
 
 This metric is calculated using the `seconds_behind_master` metric available in MariaDB's `SHOW SLAVE STATUS` command.
 
-Set an alert to inform you when the replication lag reaches a value that isn’t acceptable for your workload.
+Set an alert to inform you when the replication lag reaches a value that isn't acceptable for your workload.
 
 ## Stop replication
 
diff --git a/articles/mariadb/concepts-security.md b/articles/mariadb/concepts-security.md
@@ -5,7 +5,7 @@ author: ajlam
 ms.author: andrela
 ms.service: mariadb
 ms.topic: conceptual
-ms.date: 12/02/2019
+ms.date: 3/18/2020
 ---
 
 # Security in Azure Database for MariaDB
diff --git a/articles/mariadb/concepts-server-logs.md b/articles/mariadb/concepts-server-logs.md
@@ -5,7 +5,7 @@ author: ajlam
 ms.author: andrela
 ms.service: mariadb
 ms.topic: conceptual
-ms.date: 01/28/2020
+ms.date: 3/18/2020
 ---
 # Slow query logs in Azure Database for MariaDB
 In Azure Database for MariaDB, the slow query log is available to users. Access to the transaction log is not supported. The slow query log can be used to identify performance bottlenecks for troubleshooting.
diff --git a/articles/mariadb/concepts-servers.md b/articles/mariadb/concepts-servers.md
@@ -5,7 +5,7 @@ author: ajlam
 ms.author: andrela
 ms.service: mariadb
 ms.topic: conceptual
-ms.date: 12/02/2019
+ms.date: 3/18/2020
 ---
 # Server concepts in Azure Database for MariaDB
 This article provides considerations and guidelines for working with Azure Database for MariaDB servers.
diff --git a/articles/mariadb/concepts-supported-versions.md b/articles/mariadb/concepts-supported-versions.md
@@ -5,7 +5,7 @@ author: ajlam
 ms.author: andrela
 ms.service: mariadb
 ms.topic: conceptual
-ms.date: 09/12/2019
+ms.date: 03/18/2020
 ---
 # Supported Azure Database for MariaDB server versions
 
diff --git a/articles/mariadb/connect-workbench.md b/articles/mariadb/connect-workbench.md
@@ -6,7 +6,7 @@ ms.author: andrela
 ms.service: mariadb
 ms.custom: mvc
 ms.topic: quickstart
-ms.date: 12/02/2018
+ms.date: 3/18/2020
 ---
 
 # Azure Database for MariaDB: Use MySQL Workbench to connect and query data
