Gazareth (1/23/2013)
dwain.c (1/22/2013)
Upon reflection, I realized that capturing the UserID that deleted the record is not possible in the TRIGGER itself.So I went back and modified the code to show you how it could be done. I don't particularly like it but it works and maybe someone has a better idea.
SUSER_SNAME() / ORIGINAL_LOGIN() ?
As those would be associated with SQL Server, they may bear no relation to the application login, which is most likely what you'd want to capture.
My thought question: Have you ever been told that your query runs too fast?
My advice:
INDEXing a poor-performing query is like putting sugar on cat food. Yeah, it probably tastes better but are you sure you want to eat it?
The path of least resistance can be a slippery slope. Take care that fixing your fixes of fixes doesn't snowball and end up costing you more than fixing the root cause would have in the first place.
Need to UNPIVOT? Why not CROSS APPLY VALUES instead?[/url]
Since random numbers are too important to be left to chance, let's generate some![/url]
Learn to understand recursive CTEs by example.[/url]
[url url=http://www.sqlservercentral.com/articles/St