I don't follow you.
Here's the scenario I'm talking about:
Table1 has a logging trigger on it that follows the "after-only" model I wrote about, because it's usual use is 10-20 updates per insert, and this results in a smaller log table.
You insert data into it. This is NOT logged.
I update the data in it. This is logged, but only what I changed it to, not what it was changed from.
Management needs to know what it was changed from and to, as part of a report.
How does a join get that information in this scenario?
- Gus "GSquared", RSVP, OODA, MAP, NMVP, FAQ, SAT, SQL, DNA, RNA, UOI, IOU, AM, PM, AD, BC, BCE, USA, UN, CF, ROFL, LOL, ETC
Property of The Thread
"Nobody knows the age of the human race, but everyone agrees it's old enough to know better." - Anon