Is SELECT * ok in a Trigger. Or am I asking for trouble?
Typically, it is considered "lazy" programming.

Given that you're specifically inserting two values into your TestAudit table here, I'd be careful to make sure your select is also getting exactly two values. Because if, for some reason, that Test table has or ever gets a third column, this trigger will fail.

Not directly related to your question but if you're setting up an audit table,  I'd also add some additional columns to your TestAudit table to...


track the action you are auditing (delete in this case, vs inserts or updates)
date/time column to track when the audit event occurred
user ID column to track who carried out the action you are auditing.


So that results in a query like:

INSERT dbo.TestAudit([ID], [Person], [AuditAction], [ChangedOn], [ChangedBy])
SELECT [ID], [Person], 
   'Delete', -- or a 'D' or a numeric lookup to an audit actions table...
   GetDate(), -- or SYSDATETIME() for greater precision
   SYSTEM_USER -- or some other value for WHO made the deletion
FROM deleted


That way you're getting the exact columns you need and you're auditing what/when/why/who the audit event is about.