DROP ASSEMBLY (Transact-SQL)
Applies to: SQL Server Azure SQL Managed Instance
Removes an assembly and all its associated files from the current database. Assemblies are created by using CREATE ASSEMBLY and modified by using ALTER ASSEMBLY.
Transact-SQL syntax conventions
DROP ASSEMBLY [ IF EXISTS ] assembly_name [ ,...n ] [ WITH NO DEPENDENTS ] [ ; ]
To view Transact-SQL syntax for SQL Server 2014 and earlier, see Previous versions documentation.
Applies to: SQL Server ( SQL Server 2016 (13.x) through current version).
Conditionally drops the assembly only if it already exists.
Is the name of the assembly you want to drop.
WITH NO DEPENDENTS
If specified, drops only assembly_name and none of the dependent assemblies that are referenced by the assembly. If not specified, DROP ASSEMBLY drops assembly_name and all dependent assemblies.
Dropping an assembly removes an assembly and all its associated files, such as source code and debug files, from the database.
If WITH NO DEPENDENTS is not specified, DROP ASSEMBLY drops assembly_name and all dependent assemblies. If an attempt to drop any dependent assemblies fails, DROP ASSEMBLY returns an error.
DROP ASSEMBLY returns an error if the assembly is referenced by another assembly that exists in the database or if it is used by common language runtime (CLR) functions, procedures, triggers, user-defined types or aggregates in the current database.
DROP ASSEMBLY does not interfere with any code referencing the assembly that is currently running. However, after DROP ASSEMBLY executes, any attempts to invoke the assembly code will fail.
Requires ownership of the assembly, or CONTROL permission on it.
The following example assumes the assembly
HelloWorld is already created in the instance of SQL Server.
DROP ASSEMBLY Helloworld ;
CREATE ASSEMBLY (Transact-SQL)
ALTER ASSEMBLY (Transact-SQL)
Getting Information About Assemblies