Azure Database for PostgreSQL - Single Server is being retired on 28 March 2025
In Spring 2018 we announced the general availability of the inaugural fully managed PostgreSQL database service, Azure Database for PostgreSQL – Single Server. Since that release five years ago, we have invested time and resources in Azure Database for PostgreSQL to make it an intelligent, scalable, and reliable database that is best for running your open source PostgreSQL workloads at a lower cost than running them on-premises or on a virtual machine.
In November 2021 we released the next generation deployment option in Azure Database for PostgreSQL - Flexible Server, which provides better price-performance, a simplified developer experience, and support for the latest PostgreSQL versions.
As we continue to invest in Azure Database for PostgreSQL and focus our efforts on Flexible Server to make it the best destination for your open source PostgreSQL workloads, we have decided to retire Single Server in two years (March 2025) to ensure we are providing the best user experience for our customers.
To assist you with this move, we announced the general availability of the Single Server to Flexible server migration tool this week to ensure a simple and easy migration experience.
When you migrate to Azure Database for PostgreSQL - Flexible Server, you'll have access to multiple improvements, including:
- Support for Postgres version 11 and newer, plus built-in security enhancements.
- Better price-performance with support for burstable tier compute options.
- Improved uptime with the ability to configure a hot standby on the same or a different zone and user-controlled maintenance windows.
- A simplified developer experience for high-performance data workloads.
- Additional improvements include Linux-based VMs, premium managed disks, connection pooling with PgBouncer, and more.
Common FAQ's to consider with the retirement announcement
We understand you may have a lot of questions about what this announcement means for your Azure Database for PostgreSQL – Single Server workloads, so we have prepared an FAQ to review as you plan your migration. We have included a few common FAQ's below:
Q. Will there be future updates to Single Server to support the latest PostgreSQL versions?
A. We recommend you migrate to Flexible Server if you must run on the latest PostgreSQL engine versions. We will continue to deploy minor versions released by the community for Postgres version 11 until it's retired by the community in Nov'2023.
Q. What happens to my existing Azure Database for PostgreSQL - Single Server instances?
A. Your existing Azure Database for PostgreSQL - Single Server workloads will continue to be supported until March 2025.
Q. What if I still need to create a new single servers to meet my business needs after the Azure Database for PostgreSQL - Single Server announcement?
A. We aren't stopping the ability to create new single servers immediately, so you can continue to create new single servers through CLI to meet your business needs for all PostgreSQL versions supported on Azure Database for PostgreSQL – Single Server. We strongly encourage you to explore Flexible Server and are confident that it will meet your business needs. Don't hesitate to contact us so we can help suggest the best path forward for you.
Note: We are extending support for Postgres version 11 past the community retirement date and will support PostgreSQL version 11 on both Single Server and Flexible Server to ease this transition. Consider migrating to Flexible Server to use the benefits of the latest Postgres engine versions.
If you would like to get answers from community experts, check out Microsoft Q&A.
