AWS RDS SQL Server unable to drop database

后端 未结 4 1901
慢半拍i
慢半拍i 2021-01-02 02:23

I tried to migrate a SQL Server database by Export Data-tier Application (.bacpac file) from an Amazon RDS instance to other, but import didn\'t succeed. So now

相关标签:
4条回答
  • 2021-01-02 02:56

    Sounds like your not a member of the correct role.

    https://msdn.microsoft.com/en-us/library/ee240822.aspx

    Permissions

    A DAC can only be deleted by members of the sysadmin or serveradmin fixed server roles, or by the database owner. The built-in SQL Server system administrator account named sa can also launch the wizard.

    https://msdn.microsoft.com/en-us/library/ms178613.aspx

    Permissions

    SQL Server - Requires the CONTROL permission on the database, or ALTER ANY DATABASE permission, or membership in the db_owner fixed database role.

    Azure SQL Database - Only the server-level principal login (created by the provisioning process) or members of the dbmanager database role can drop a database.

    Parallel Data Warehouse - Requires the CONTROL permission on the database, or ALTER ANY DATABASE permission, or membership in the db_owner fixed database role.

    0 讨论(0)
  • 2021-01-02 02:57

    If your database is in a Multi-AZ deployment, then you need to run this command to drop those databases:

    EXECUTE msdb.dbo.rds_drop_database N'DBName'
    
    0 讨论(0)
  • 2021-01-02 03:02

    This is the answer for an old thread but who knows, it might help someone having the same issue.

    I run into the same problem, but in my case, my database was in offline mode. If the database is in offline mode, it won't allow you to drop it with the drop command. first, you should bring the database back online by running this sp and then execute the drop table command.

    EXEC rdsadmin.dbo.rds_set_database_online databasename
    
    0 讨论(0)
  • 2021-01-02 03:06

    I ran into this same issue. After trying to restore a database via SSMS using a .bacpac, it fails and leaves you with a database that you appear to not have permissions to drop.

    A workaround, is to use the rdsadmin rename function to rename it to something else, which then seems to fix the permission issue and allows you to drop it.

    EXEC rdsadmin.dbo.rds_modify_db_name N'<OldName>', N'<NewName>'
    

    Then just drop the DB. Hope that helps someone else in the same predicament.

    0 讨论(0)
提交回复
热议问题