DROP EVENT NOTIFICATION (Transact-SQL)

notification_name

Is the name of the event notification to remove. Multiple event notifications can be specified. To see a list of currently created event notifications, use sys.event_notifications (Transact-SQL).

SERVER

Indicates the scope of the event notification applies to the current server. SERVER must be specified if it was specified when the event notification was created.

DATABASE

Indicates the scope of the event notification applies to the current database. DATABASE must be specified if it was specified when the event notification was created.

QUEUE queue_name

Indicates the scope of the event notification applies to the queue specified by queue_name. QUEUE must be specified if it was specified when the event notification was created. queue_name is the name of the queue and must also be specified.

If an event notification fires within a transaction and is dropped within the same transaction, the event notification instance is sent, and then the event notification is dropped.

To drop an event notification that is scoped at the database level, at a minimum, a user must be the owner of the event notification or have ALTER ANY DATABASE EVENT NOTIFICATION permission in the current database.

To drop an event notification that is scoped at the server level, at a minimum, a user must be the owner of the event notification or have ALTER ANY EVENT NOTIFICATION permission in the server.

To drop an event notification on a specific queue, at a minimum, a user must be the owner of the event notification or have ALTER permission on the parent queue.

The following example creates a database-scoped event notification, then drops it:

USE AdventureWorks;
GO
CREATE EVENT NOTIFICATION NotifyALTER_T1
ON DATABASE
FOR ALTER_TABLE
TO SERVICE 'NotifyService',
    '8140a771-3c4b-4479-8ac0-81008ab17984';
GO
DROP EVENT NOTIFICATION NotifyALTER_T1
ON DATABASE;

Reference