Skip to content

Commit 3b7a125

Browse files
committed
Adding FAQ
1 parent 05c602d commit 3b7a125

File tree

1 file changed

+5
-1
lines changed

1 file changed

+5
-1
lines changed

articles/mysql/single-server/whats-happening-to-mysql-single-server.md

Lines changed: 5 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -74,7 +74,11 @@ A. Unfortunately, we don't plan to support Single Server beyond the sunset date
7474

7575
**Q. After the Single Server retirement announcement, what if I still need to create a new single server to meet my business needs?**
7676

77-
A. As part of this retirement, we will no longer support creating new Single Server instances from the Azure portal beginning **January 16, 2023**. If you still need to create Single Server instances to meet business continuity needs, you can leverage [Azure CLI](./quickstart-create-mysql-server-database-using-azure-cli.md).
77+
A. As part of this retirement, we will no longer support creating new Single Server instances from the Azure portal beginning **January 16, 2023**. If you still need to create Single Server instances to meet business continuity needs, you can leverage [Azure CLI](./quickstart-create-mysql-server-database-using-azure-cli.md).
78+
79+
**Q. After the Single Server retirement announcement, what if I still need to create a new read replica for my single server instance?**
80+
81+
A. You will still be able to create read replicas for your existing single server instance from the **Replication blade** and this will continue to be supported till the sunset date of **September 16, 2024**.
7882

7983
**Q. Are there additional costs associated with performing the migration?**
8084

0 commit comments

Comments
 (0)