Defect: Server name is already used
I created a new server and new database in Azure SQL. I had to delete that server and now I am trying to create server with same name. But it says that server name is already used. I could also reproduce same scenario.
Apologies for the delay in responding here. I know we did have a bug earlier this year. Can you please confirm if this issue is fixed or you are still having the issue.
Bruno Pugioli commented
yes, still happening
Ihor Kliushnikov commented
We had a discussion about this topic at MSDN forum: https://social.msdn.microsoft.com/Forums/en-US/0bcf17c3-00ea-4959-94a6-ddd77002bb85/inconsistency-with-azure-sql-server-deletion
To give a brief summary: my biggest problem with this case is no meaningful error response from resource provisioning operation: deployment is just hanging... If reserving names for a while is desired behavior - just return an error response to your users immediately. And here I mean all users: go or python libraries, ARM templates, etc.
Haitham Elrefaie commented
I was trying to creat the new server at deferent zone, with the same name and it didn't work, when I tried to creat it again at the same zone it didn't as well, but after 1-2 hours I the server appeared in the sql server service at the original zone.
I do not know if this is how it was supposed to work or I was lucky, but I'm happy.
- This is my advice and might help: If you want to recreate the deleted sql server it should be within two days from deletion + it should be at the same zone, after your attempt to recreat if you got the error, wait 1-2 hours and it should be in your sql server service page.
Matt McLoughlin commented
This is still an issue. After deleting a resource group (and the portal and ARM indicates it has been successfully deleted) attempting to create a SQL Server instance with the same name as the deleted one results in the error "[servername] is busy with another operation. Please try your operation later." This automatically resolves after 5 minutes or so, but the Resource should not indicate that deletion is successful until it is truly available to be recreated.
it was not fixed
The issue doesn't fixed
Malcolm Gates commented
This is still an issue. I just deleted a SQL Server entry, and now I am trying to create a new SQL Server with the same name in a different subscription, and I get this message: "Specified server name is already used".
How long does it take for the name to become available again? Why isn't it available immediately?
Christian D. commented
Same issue. I understand the default behavior is "protective" but it would be nice when deleting to have a checkbox that allows to "release" the name for use on other subscriptions and/or resource groups (and in the ARM Template or API as well of course).
In a DEV/TEST cycle this is very annoying...
I have the same problem as of 25.02.2016.
Milen Pavlov commented
Same here, it takes at least couple of hours (or a day) for the name to be available again...
Michael Catalfano commented
@Ronak: I found this article which suggests that the name is locked for at least 5 days and that currently only Azure support can clear the metadata:
Michael Catalfano commented
Same scenario for me and I am also encountering this error. I deleted an Azure SQL DB, the related server and resource group. Worked through the interface to provision a new Azure SQL DB and received the error "Error: Specified Server Name is already used" message. I am not finding this existing VM in any of the other Azure blades to suggest there should be a conflict.