We know about triggers as they exist in SQL Server 2000 and its previous versions ? triggers that fire in response to INSERT, UPDATE and DELETE events.

You will need to write 'instead of insert/update/delete' triggers (talking SQL Server syntax here) that will handle any of those operations on those views and that propagate the changes to the new ...

Most of the time, it could save the changes with maybe 2-3 UPDATE statements, and that's it.<BR><BR>So, like the title says, I want to find out what SQL statement caused a trigger to fire. have ...