BR><BR>So, like the title says, I want to find out what SQL statement caused a trigger to fire. have full access to the SQL server, but not to the source of the program. PeterB suggested in IRC ...

AWS today announced a new database product that is clearly meant to go after Microsoft ... but also SQL commands, cursors, catalog views, data types, triggers, stored procedures and functions.