@Andy Wybenga Depending on the size of the database it could take a while for the databases to get deleted automatically.
Please let us know if you are still facing this issue.
Inconsistant database state between Azure Portal and SSMS
While learning how to use the Azure Database Migration service, I had a migration from on prem to an SQL Managed Instance get stuck. I cancelled and deleted the migration project, but the two databases I was migrating now seem to be stuck in a bad state. From the Managed Instance overview in the Azure Portal, I don't see either of the databases, but when I connect to the Managed Instance via SSMS they're both there. Originally they were showing a "Restoring..." status. They're currently in a "Recovery Pending" state. Retrying the migration fails, because the target databases already exist, even though they don't show in the portal.
Does anyone have any idea how to get rid of these databases, so I can start over? I've tried dropping the databases from SSMS, but I get an error stating the database doesn't exist.
Thanks for any help you can give!
-
KalyanChanumolu-MSFT 8,331 Reputation points
2020-08-10T10:04:42.643+00:00