Skip to content

Commit aa379c0

Browse files
Merge pull request #255633 from karla-escobar/docs-editor/whats-happening-to-mariadb-1692653415
Docs editor/whats happening to mariadb 1692653415
2 parents c744644 + ce651f7 commit aa379c0

File tree

1 file changed

+6
-2
lines changed

1 file changed

+6
-2
lines changed

articles/mariadb/whats-happening-to-mariadb.md

Lines changed: 6 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -14,7 +14,7 @@ ms.custom: deprecation announcement
1414

1515
Azure Database for MariaDB is on the retirement path, and **Azure Database for MariaDB is scheduled for retirement by September 19, 2025**.
1616

17-
As part of this retirement, there is no extended support for creating new MariaDB server instances from the Azure portal beginning **December 19, 2023**, if you still need to create MariaDB instances to meet business continuity needs, you can use [Azure CLI](/azure/mysql/single-server/quickstart-create-mysql-server-database-using-azure-cli) until **March 19, 2024**.
17+
As part of this retirement, there is no extended support for creating new MariaDB server instances from the Azure portal beginning **January 19, 2024**, if you still need to create MariaDB instances to meet business continuity needs, you can use [Azure CLI](/azure/mysql/single-server/quickstart-create-mysql-server-database-using-azure-cli) until **March 19, 2024**.
1818

1919
We're investing in our flagship offering of Azure Database for MySQL - Flexible Server better suited for mission-critical workloads. Azure Database for MySQL - Flexible Server has better features, performance, an improved architecture, and more controls to manage costs across all service tiers compared to Azure Database for MariaDB. We encourage you to migrate to Azure Database for MySQL - Flexible Server before retirement to experience the new capabilities of Azure Database for MySQL - Flexible Server.
2020

@@ -54,7 +54,11 @@ A. Unfortunately, we don't plan to support Azure Database for MariaDB beyond the
5454

5555
**Q. After the Azure Database for MariaDB retirement announcement, what if I still need to create a new MariaDB server to meet my business needs?**
5656

57-
A. As part of this retirement, we'll no longer support creating new MariaDB instances from the Azure portal beginning **December 19, 2023**. Suppose you still need to create MariaDB instances to meet business continuity needs. In that case, you can use [Azure CLI](/azure/mysql/single-server/quickstart-create-mysql-server-database-using-azure-cli) until **March 19, 2024**.
57+
A. As part of this retirement, we'll no longer support creating new MariaDB instances from the Azure portal beginning **January 19, 2024**. Suppose you still need to create MariaDB instances to meet business continuity needs. In that case, you can use [Azure CLI](/azure/mysql/single-server/quickstart-create-mysql-server-database-using-azure-cli) until **March 19, 2024**.
58+
59+
**Q. Will I be able to restore instances of Azure Database for MariaDB after March 19, 2024?**
60+
61+
A. Yes, you will be able to restore your MariaDB instances from your existing servers until September 19, 2025.
5862

5963
**Q. How does the Azure Database for MySQL flexible server's 99.99% availability SLA differ from MariaDB?**
6064

0 commit comments

Comments
 (0)