|
|
|
SSCoach
         
Group: General Forum Members
Last Login: Yesterday @ 1:55 PM
Points: 15,442,
Visits: 9,571
|
|
Some expansions on this subject at:
http://www.sqlservercentral.com/Forums/Topic536927-145-1.aspx
- 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
|
|
|
|
|
SSC Veteran
      
Group: General Forum Members
Last Login: Monday, May 13, 2013 2:01 PM
Points: 295,
Visits: 393
|
|
Gsquared,
Thanks for the informative article.
One question though. My question is to know if there is any advantage of one method over the other. Or is it just preference (...I say toMato and you say TomaTo case)
In part II, active logging with triggers, on INSERT the code stores the INSERTED record. On DELETE, it stores the DELETED record. But on UPDATE it stores the new record from the INSERTED table rather than the row that is being deleted.
I've always stored the row that is being deleted (i.e. from DELETED table except for INSERT).
I see both methods to be of same value. but wanted to know what you think of it.
thanks, _UB
SqlTimes Blog on Sql Server
|
|
|
|
|
SSC Veteran
      
Group: General Forum Members
Last Login: Saturday, May 18, 2013 5:49 AM
Points: 202,
Visits: 1,043
|
|
I am curious, that no one has yet commented over CDC feature built-in in SQL Server 2008? It is not such out off the domain of Auditing?
Please?
|
|
|
|