locked
Trying to delete a SQL Server and getting an error code 409 in the response RRS feed

  • Question

  • Hi all,

    I am trying to delete a SQL Server that I created for testing purposes, but when I try to delete the Server (from both UI and CLI) I ended up getting a message indicating that the operation has failed with ErrorCode: 409 in the UI and the error message "Deployment failed. Correlation ID: xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxx. Server 'sqldbtest01' is busy with another operation. Please try your operation later."

    The server state shows as "disabled".

    Any ideas of what is going on?

    Tks in advance

    Thursday, May 28, 2020 1:40 PM

All replies

  • Hi all,

    I am trying to delete a SQL Server that I created for testing purposes, but when I try to delete the Server (from both UI and CLI) I ended up getting a message indicating that the operation has failed with ErrorCode: 409 in the UI and the error message "Deployment failed. Correlation ID: xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxx. Server 'sqldbtest01' is busy with another operation. Please try your operation later."

    The server state shows as "disabled".

    Any ideas of what is going on?

    Tks in advance

    Good day acezar,

    >> I am trying to delete a SQL Server

    I assume that you are speaking about Azure SQL Logical Server and NOT "SQL Server".

    This issue is with your specific service and someone will probably need to have a look at this entity which mean that you need to open a ticket in your subscription so the team will be able to find the issue. This is not a generic issue which we can solve in the forum as much as I can understand from your description.


    signature   Ronen Ariely
     [Personal Site]    [Blog]    [Facebook]    [Linkedin]

    Friday, May 29, 2020 2:07 AM
  • Did the database get cleaned up or are you still in need of assistance with this issue?

    Regards,

    Mike

    Monday, June 1, 2020 7:48 PM
  • Its been a while we heard from you. We are hoping that your issue is resolved.

    If you are still facing any issue, please let us know or reach out to Azure support.

    Wednesday, June 3, 2020 6:05 AM