Sadly I could not find out.
Going forward – To capture deletes on a table I set-up a regular ‘after delete’ trigger with some extra columns to hold system functions.
This allowed me to capture the date/time, PC-Name and login that originated deletes. Here is my working lab …
--lab_trigger_deletes.sql --create table to be monitored and add some data CREATE TABLE t1 (c1 INT, c2 int) INSERT INTO t1 VALUES (1,7), (2,8), (3,9) -- create audit table CREATE TABLE t1_audit (c1 INT, c2 INT, c3 DATETIME, c4 SYSNAME, c5 SYSNAME, c6 SYSNAME) -- check contents of both tables SELECT * from t1 SELECT * FROM t1_audit -- create trigger CREATE TRIGGER trg_ItemDelete ON dbo.t1 AFTER DELETE AS INSERT INTO dbo.t1_audit(c1, c2, c3, c4, c5, c6) SELECT d.c1, d.c2, GETDATE(), HOST_NAME(), SUSER_SNAME(), ORIGINAL_LOGIN() FROM Deleted d -- delete a row (firing the trigger) DELETE FROM t1 WHERE c1 = 2 -- check contents of both tables again SELECT * from t1 SELECT * FROM t1_audit -- tidy up IF OBJECT_ID ('trg_ItemDelete', 'TR') IS NOT NULL DROP TRIGGER trg_ItemDelete; drop TABLE t1 drop TABLE t1_audit