General Availability
Organizations evolve, and so do their infrastructure and naming standards. Whether standardizing resource names, reorganizing environments, or recovering from a regional outage, customers often need to change the identity of an existing database server.
Until now, server names in Azure Database for MySQL have been immutable. Changing a server name required customers to provision a new server, migrate data, update application connection strings, and plan for downtime. This also introduced additional operational complexity around backups and recovery.
We're introducing general availability of Server Rename, a capability that allows customers to rename an existing Azure MySQL server with minimal downtime, without deleting and recreating the server.
Why Server Rename
When provisioning an Azure Database for MySQL, customers specify a server name that becomes part of its hostname. Until now, this name has been immutable. This has created challenges for organizations that need to align their database infrastructure with evolving business and operational requirements.
Consider a few common situations:
- An organization standardizes its resource naming conventions and needs to rename existing database servers to comply with the new standards.
- A development or staging environment is promoted to production, and the database server needs to adopt the production server's original name.
- A database is restored to a new server, and administrators want to restore the original server identity without requiring application-level connection string changes.
- During disaster recovery, a read replica is promoted to become the primary server and needs to assume the original server's name.
Historically, addressing these scenarios could require provisioning a new server, migrating data, updating application connection strings, coordinating downtime, and managing backup and recovery considerations. In some cases, customers had to delete and recreate their database servers simply to change the hostname.
Server Rename removes this operational barrier by providing a streamlined renaming experience with minimal downtime.
Key scenarios and use cases
| Scenario | How server rename helps |
| Naming standardization | Align existing server names with organization-wide naming conventions without server recreation or migration. |
| Server restoration | Rename a restored server to match the original server name, minimizing application connection string changes. |
| Major version upgrades | Upgrade a read replica, validate, promote it, and rename it to the original primary server name. |
| Regional disaster recovery | Promote a cross-region read replica and rename it to the original source server name to simplify application recovery. |
| Deployment testing and validation | Similar to the concept of blue-green deployments, promote the validated environment and rename it to the original server name for a smoother production transition. |
| Environment reorganization | Rename servers when consolidating or reorganizing development, staging, and production environments. |
How to rename a server
Renaming your Azure Database for MySQL and can be initiated directly from the Azure portal or using Azure CLI.
-
Sign in to the Azure portal and navigate to your Azure Database for MySQL instance.
-
On the Overview blade, select the Rename server button. It will open rename server panel on the right.
-
Enter the new server name and review the rename details.
-
Confirm the operation to initiate the rename.
-
Rename can also be performed using Change next to the Endpoint field under Essentials in the Azure portal.
Getting Started:
Ready to get started? Review the product documentation for supported configurations, prerequisites, and guidance on renaming your Azure Database for MySQL server.
If you have any questions or need guidance, don't hesitate to reach out to us at Ask Azure DB for MySQL.