This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(6.4, 20%, 10%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EAW%3C/text%3E%3C/svg%3E)
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!
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(25.6, 10%, 12%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EKM%3C/text%3E%3C/svg%3E)
@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.
Thanks for getting back to me! I left things over the weekend, and the portal and SSMS are now back to a consistent state