If by "update a report table" you mean inserting into it, the trigger is just fine. Something else is going and you just need to find it. Perhaps a long winded explicit transaction is to blame.
As to "quieting managment" by taking a shortcut goes, don't do it. If you do something to make it "good enough" (and it won't be... it'll catch ya again in the future), you won't be given the time to go back and fix it correctly.
is pronounced ree-bar and is a Modenism for R
First step towards the paradigm shift of writing Set Based code: Stop thinking about what you want to do to a row... think, instead, of what you want to do to a column.
Although they tell us that they want it real bad, our primary goal is to ensure that we dont actually give it to them that way.
Although change is inevitable, change for the better is not.
Just because you can do something in PowerShell, doesnt mean you should. Helpful Links:
How to post code problemsHow to post performance problemsForum FAQs