I have a question regarding the Inserted and Deleted tables populated during the firing of a trigger. This would be in a situation where a single trigger has been fired multiple times by several concurrent operations against a table. For the purpose of this question let's say they were update operations against "TableA".
Are the inserted and deleted tables scoped to the current session? In other words will they only contain the inserted and deleted records for the current scope, or will they contain the records for all current update operations against the same table? Can there even be truely concurrent operations or will locks prevent this?
All I really need to know is that no matter how much traffic the database gets, that these tables will only contain the data for the current scope and operation.
Thanks in advance for all the help!
Nathon Dalton
Sr. Software Engineer
Blog: http://nathondalton.wordpress.com