So I've got a silly question. Don't triggers only handle one row at a time?
For instance, I've got an "after update" trigger on a table. If I run a query that updates 20 records in one update statement for that table, it's treated as 20 separate transactions, and the trigger will run 20 separate times - once after each row is updated. It doesn't just run the trigger once for all 20 records, does it? If it does, then the inserted and deleted tables would be a lot harder to work with than I ever realized before.
The reason I'm asking is because I just ran across an "update after" trigger on our system that uses a cursor to go through the inserted table one record at a time. But if I'm understanding correctly, the inserted and deleted tables will never have more than one record, right? So that cursor just seems pointless to me.
I haven't worked with triggers that much in the past, but I thought I understood the basics pretty well, so this one had me confused.