Transact-SQL Syntax ConventionsRemoves one or more user databases or database snapshots from an instance of SQL Server
Transact-SQL Syntax Conventions
-- SQL Server Syntax
DROP DATABASE [ IF EXISTS ] { database_name | database_snapshot_name } [ ,...n ] [;] -- Azure SQL Database, Azure SQL Data Warehouse and Parallel Data Warehouse Syntax
DROP DATABASE database_name [;] IF EXISTS
Applies to: SQL Server SQL Server SQL Server 2016 (13.x) through current version).
Conditionally drops the database only if it already exists.
database_name
Specifies the name of the database to be removed. To display a list of databases, use the sys.databases catalog view.
database_snapshot_name
Applies to: SQL Server 2008 through SQL Server 2008 SQL Server 2017
Specifies the name of a database snapshot to be removed.
A database can be dropped regardless of its state: offline, read-only, suspect, and so on. To display the current state of a database, use the sys.databases catalog view.
A dropped database can be re-created only by restoring a backup. Database snapshots cannot be backed up and, therefore, cannot be restored.
When a database is dropped, the master database should be backed up.
Dropping a database deletes the database from an instance of SQL Server and deletes the physical disk files used by the database. If the database or any one of its files is offline when it is dropped, the disk files are not deleted. These files can be deleted manually by using Windows Explorer. To remove a database from the current server without deleting the files from the file system, use sp_detach_db.
[!WARNING]
Dropping a database that has FILE_SNAPSHOT backups associated with it will succeed, but the database files that have associated snapshots will not be deleted to avoid invalidating the backups referring to these database files. The file will be truncated, but will not be physically deleted in order to keep the FILE_SNAPSHOT backups intact. For more information, see SQL Server Backup and Restore with Microsoft Azure Blob Storage Service. Applies to: SQL Server 2016 (13.x) through current version.
Dropping a database snapshot deletes the database snapshot from an instance of SQL Server and deletes the physical NTFS File System sparse files used by the snapshot. For information about using sparse files by database snapshots, see Database Snapshots (SQL Server). Dropping a database snapshot clears the plan cache for the instance of SQL Server SQL Server Clearing the plan cache causes a recompilation of all subsequent execution plans and can cause a sudden, temporary decrease in query performance. For each cleared cachestore in the plan cache, the SQL Server SQL Server SQL Server error log contains the following informational message: “[!INCLUDEssNoVersion] has encountered %d occurrence(s) of cachestore flush for the ‘%s’ cachestore (part of plan cache) due to some database maintenance or reconfigure operations”. This message is logged every five minutes as long as the cache is flushed within that time interval.
To drop a database published for transactional replication, or published or subscribed to merge replication, you must first remove replication from the database. If a database is damaged or replication cannot first be removed or both, in most cases you still can drop the database by using ALTER DATABASE to set the database offline and then dropping it.
If the database is involved in log shipping, remove log shipping before dropping the database. For more information, see About Log Shipping (SQL Server).
System databases cannot be dropped.
The DROP DATABASE statement must run in autocommit mode and is not allowed in an explicit or implicit transaction. Autocommit mode is the default transaction management mode.
You cannot drop a database currently being used. This means open for reading or writing by any user. One way to remove users from the database is to use ALTER DATABASE to set the database to SINGLE_USER.
[!Warning] This is not a fail-proof approach, since first consecutive connection made by any thread will receive the SINGLE_USER thread, causing your connection to fail. Sql server does not provide a built-in way to drop databases under load.
Any database snapshots on a database must be dropped before the database can be dropped.
Dropping a database enable for Stretch Database does not remove the remote data. If you want to delete the remote data, you have to remove it manually.
You must be connected to the master database to drop a database.
The DROP DATABASE statement must be the only statement in a SQL batch and you can drop only one database at a time.
You must be connected to the master database to drop a database.
The DROP DATABASE statement must be the only statement in a SQL batch and you can drop only one database at a time.
Requires the CONTROL permission on the database, or ALTER ANY DATABASE permission, or membership in the db_owner fixed database role.
Only the server-level principal login (created by the provisioning process) or members of the dbmanager database role can drop a database.
Requires the CONTROL permission on the database, or ALTER ANY DATABASE permission, or membership in the db_owner fixed database role.
The following example removes the Sales database.
DROP DATABASE Sales; Applies to: SQL Server 2008 through SQL Server 2008 SQL Server 2017
The following example removes each of the listed databases.
DROP DATABASE Sales, NewSales; Applies to: SQL Server 2008 through SQL Server 2008 SQL Server 2017
The following example removes a database snapshot, named sales_snapshot0600, without affecting the source database.
DROP DATABASE sales_snapshot0600; ALTER DATABASE (Transact-SQL)
CREATE DATABASE (SQL Server Transact-SQL)
EVENTDATA (Transact-SQL)
sys.databases (Transact-SQL)