4

Created this a database from a backup.

I want to delete this database because I selected the incorrect backup. When trying to delete the database I get the following error:

Failed to delete the database: [DBNAME]. ErrorCode: 400 ErrorMessage: Cannot use reserved database name '[DBNAME]' in this operation. This is an SQL database.

Steps taken to delette database:

  1. Open Azure Portal.
  2. Select Database ([DBNAME]).
  3. Click delete button.
  4. Get above mentioned error.

Error

Error

Connecting with SSMS: The Database that I want to delete is not there DB not there

Improve this question
9
  • stackoverflow.com/questions/285775/… Commented Oct 17, 2016 at 16:35
  • @ceejayoz Is that really related here? (his question implies he was using the Azure GUI) Commented Oct 17, 2016 at 17:32
  • Have you tried deleting the database using SSMS? The GUI isn't always reliable and if you keep getting the error you'll either want to contact support, or try a manual deletion using SSMS. Btw if you can could you add some screenshots about your error? I'd like to see where you get this message. Commented Oct 17, 2016 at 17:36
  • @Reaces Given the error message, it appears the GUI isn't escaping the database name, and that OP has used a reserved word as a name. Relevant, but doesn't fully answer, hence my comment. Commented Oct 17, 2016 at 17:40
  • 1
    @LouwrensPotgieter I would really suggest you contact microsoft support for this. You have a database in the GUI that isn't showing up in SSMS, that shouldn't happen. Commented Oct 18, 2016 at 15:49

1 Answer 1

Reset to default
1

It sounds like you have used a reserved word in the DB name and for some reason the deletion process in the Azure portal isn't dealing with this. A couple of ways to deal with the immediate issue:

  • Delete the database through SQL Server Management Studio (SSMS)
  • Use SSMS to rename the database to something without a reserved word and then delete it through the portal

I would also suggest raising an bug with MS as the portal should either handle this, or prevent you from creating the DB in the first place.

Improve this answer
2
  • +1, I should have put that in an answer myself :) Commented Oct 18, 2016 at 15:49
  • Hi - i have the same problem (im using SSMS by default) - however the problem database is not listed under the database server's node in SSMS Commented Dec 21, 2016 at 9:09

You must log in to answer this question.

Start asking to get answers

Find the answer to your question by asking.

Ask question

Explore related questions

See similar questions with these tags.