Hi Kev, one way of doing this would be to append some code to your existing trigger. So when a database drop attempt is detected, you can capture the details you want (full SQL code):
I've written this - feel free to add/remove cols as you see fit:
SELECTdec.session_id, dec.connect_time, dec.protocol_type, dec.client_net_address,
dec.local_net_address, TEXT,
des.[host_name], des.[program_name], des.client_interface_name
FROM sys.dm_exec_connections dec
INNER JOIN sys.dm_exec_sessions des ON dec.session_id = des.session_id
CROSS APPLY sys.dm_exec_sql_text(most_recent_sql_handle) AS ST
You could write a sproc to drop this into a table, and/or configure with alerting (including the table contents), or similar, for automatic notification.
Derek.
---
Note to developers:Want to get the best help? Click here https://www.sqlservercentral.com/articles/forum-etiquette-how-to-post-datacode-on-a-forum-to-get-the-best-help (Jeff Moden)
My blog: http://uksqldba.blogspot.com
Visit http://www.DerekColley.co.uk to find out more about me.