Is this project still being maintained?

May 4, 2016 at 3:15 PM
Hello,

I saw the minor tweaks suggested at january were not implemented into the main version.

I'd feel alot more secure about integrating this solution if i knew it was still active :)


Thanks
May 6, 2016 at 1:57 AM
No changes since 2011.

I personally still recommend CDC in SQL Enterprise over this approach if you have that option.

The solution is not overly complicated, I actually did something very similar before I found this solution. It's just this solution wrapped it up a little nicer than my original approach.

I believe most DBA's wouldn't implement this on a heavily used or database/table though, and rightly so. Why add additional load on every update when you don't need to. It would be better to rely on polling by a SQL job based on timestamp modifications, and keeping track of the last one date/time you checked.

I only use this if;
I need to audit all the changes for a while
-Or-
The table I need to track has no timestamp field
-Or-
I don't think the application is adjusting the timestamp field in all types of updates. It's nice to have proof when you approach the vendor on this one.