数据库不会保持删除状态 [英] Database won't stay deleted

问题描述

我有一个数据库，我试图多次删除，但几分钟后它会返回并再次显示在资源列表中。我试图通过Azure门户和SQL Management工作室删除它。任何人之前都经历过这个
或者知道发生了什么？

I have a database that I've attempted to delete multiple times, however after a few minutes it returns and is shown again in the resource list. I've attempted to delete it through the Azure Portal and through SQL Management studio. Anyone experienced this before or know what's going on??

推荐答案

我有一个数据库，我试图多次删除，但是几分钟后它返回并再次显示在资源列表中。我试图通过Azure门户和SQL Management工作室删除它。任何人以前经历过
或者知道发生了什么？

I have a database that I've attempted to delete multiple times, however after a few minutes it returns and is shown again in the resource list. I've attempted to delete it through the Azure Portal and through SQL Management studio. Anyone experienced this before or know what's going on??

美好的一天<？！？>

Good day <?!?>

这是当我们忘记与"简单"工作时我们遇到的问题SQL Server幕后。我的意思是当我们点击"删除"时在门户网站中，它并不意味着数据库是来自服务器的DROP： - ）

This is part of the issues which we have when we forget that we works with "simple" SQL Server behind the scenes. I mean that when we click "delete" in the portal, it does not yet mean that the database was DROP from the server :-)

根据您的描述，我知道您试图从Portal中删除数据库并且; DROP DATABASE"行动没有完成。但是，由于您正在使用Portal，您正在使用一种服务来隐藏来自服务器的真实错误消息
。

According to your description I understand that you tried to delete the database from the Portal and the "DROP DATABASE" action did not completed. But since you are using the Portal you are working behind a service which hides the real error messages coming from the server.

似乎您的数据库从未丢弃过一个问题（例如某人正在使用此数据库来阻止DROP，例如Azure Sync服务或其他东西）

It seems that your database was never Dropped since there was an issue (for example someone is using this database for something that prevents the DROP, like Azure Sync service or something else)

步骤1：您应首先确认您没有任何服务使用此数据库。 

Step 1: You should first confirm that you do not have any service which uses this database. 

步骤2：您可以使用直接方法绕过大多数（并非所有，因为我们实际上并不是控制实例而是虚拟服务器）的限制，含义使用SSMS或ADS连接到虚拟服务器，只需执行"DROP DATABASE"即可。查询，
但这可能导致基于此数据库的其他服务中出现意外行为（这就是为什么我们有第1步） 

Step 2: You can bypass most (not all, since we do not really control the instance but a virtual server) of the limitations using a direct approach, meaning Connect to the virtual server using SSMS or ADS and simply execute a "DROP DATABASE" query, BUT this might lead to un-expected behavior in other services which based on this database(which is why we have step 1) 

这样，你会至少在SSMS中收到错误信息，你会更多地了解原因

This way, you will at least get the error message in the SSMS and you will know more about the reason

这篇关于数据库不会保持删除状态的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！