Skip to content

Commit 489c62a

Browse files
committed
MySQL freshness
1 parent 90765fa commit 489c62a

10 files changed

+13
-13
lines changed

articles/mysql/concept-reserved-pricing.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,7 @@ author: kummanish
55
ms.author: manishku
66
ms.service: mysql
77
ms.topic: conceptual
8-
ms.date: 12/02/2019
8+
ms.date: 3/18/2020
99
---
1010

1111
# Prepay for Azure Database for MySQL compute resources with reserved capacity
@@ -46,8 +46,8 @@ The following table describes required fields.
4646
| Field | Description |
4747
| :------------ | :------- |
4848
| Subscription | The subscription used to pay for the Azure Database for MySQL reserved capacity reservation. The payment method on the subscription is charged the upfront costs for the Azure Database for MySQL 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.
49-
| Scope | The vCore reservations 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 MySQL 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 MySQL servers in this subscription. </br></br> **Single resource group**, the reservation discount is applied to Azure Database for MySQL servers in the selected subscription and the selected resource group within that subscription.
50-
| Region | The Azure region thats covered by the Azure Database for MySQL reserved capacity reservation.
49+
| 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 MySQL 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 MySQL servers in this subscription. </br></br> **Single resource group**, the reservation discount is applied to Azure Database for MySQL servers in the selected subscription and the selected resource group within that subscription.
50+
| Region | The Azure region that's covered by the Azure Database for MySQL reserved capacity reservation.
5151
| Deployment Type | The Azure Database for MySQL resource type that you want to buy the reservation for.
5252
| Performance Tier | The service tier for the Azure Database for MySQL servers.
5353
| Term | One year

articles/mysql/concepts-aks.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,7 @@ author: ajlam
55
ms.author: andrela
66
ms.service: mysql
77
ms.topic: conceptual
8-
ms.date: 12/02/2019
8+
ms.date: 3/18/2020
99
---
1010

1111

articles/mysql/concepts-audit-logs.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,7 @@ author: ajlam
55
ms.author: andrela
66
ms.service: mysql
77
ms.topic: conceptual
8-
ms.date: 12/09/2019
8+
ms.date: 3/18/2020
99
---
1010

1111
# Audit Logs in Azure Database for MySQL

articles/mysql/concepts-backup.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,7 @@ author: ajlam
55
ms.author: andrela
66
ms.service: mysql
77
ms.topic: conceptual
8-
ms.date: 12/02/2019
8+
ms.date: 3/18/2020
99
---
1010

1111
# Backup and restore in Azure Database for MySQL

articles/mysql/concepts-business-continuity.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,7 @@ author: ajlam
55
ms.author: andrela
66
ms.service: mysql
77
ms.topic: conceptual
8-
ms.date: 12/02/2019
8+
ms.date: 3/18/2020
99
---
1010

1111
# Understand business continuity in Azure Database for MySQL
@@ -28,7 +28,7 @@ The following table compares the ERT and RPO for the available features:
2828
2929
## Recover a server after a user or application error
3030

31-
You can use the services 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.
31+
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.
3232

3333
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.
3434

articles/mysql/concepts-compatibility.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,7 @@ author: ajlam
55
ms.author: andrela
66
ms.service: mysql
77
ms.topic: conceptual
8-
ms.date: 12/05/2019
8+
ms.date: 3/18/2020
99
---
1010
# MySQL drivers and management tools compatible with Azure Database for MySQL
1111
This article describes the drivers and management tools that are compatible with Azure Database for MySQL.

articles/mysql/concepts-connection-libraries.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,7 @@ author: ajlam
55
ms.author: andrela
66
ms.service: mysql
77
ms.topic: conceptual
8-
ms.date: 12/02/2019
8+
ms.date: 3/18/2020
99
---
1010

1111
# Connection libraries for Azure Database for MySQL

articles/mysql/concepts-connectivity.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -6,7 +6,7 @@ author: jan-eng
66
ms.author: janeng
77
ms.service: mysql
88
ms.topic: conceptual
9-
ms.date: 12/02/2019
9+
ms.date: 3/18/2020
1010
---
1111

1212
# Handle transient errors and connect efficiently to Azure Database for MySQL

articles/mysql/concepts-data-access-and-security-threat-protection.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,7 @@ author: ajlam
55
ms.author: andrela
66
ms.service: mysql
77
ms.topic: conceptual
8-
ms.date: 12/02/2019
8+
ms.date: 3/18/2020
99
---
1010
# Azure Database for MySQL Advanced Threat Protection
1111

articles/mysql/concepts-data-access-and-security-vnet.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,7 @@ author: ajlam
55
ms.author: andrela
66
ms.service: mysql
77
ms.topic: conceptual
8-
ms.date: 12/02/2019
8+
ms.date: 3/18/2020
99
---
1010
# Use Virtual Network service endpoints and rules for Azure Database for MySQL
1111

0 commit comments

Comments
 (0)