|Related to : Change Data Capture or Change Tracking - Same as Traditional Audit Trail Table?|
|Linq to SQL Audit Trail / Audit Log: should I use triggers or doddleaudit?|
I'm working on a business app that requires that ALL database
transactions be audited (for legal purposes mainly).
looked around the web and came across DoddleAudit
(http://www.codeplex.com/DoddleAudit) which basically adds the ability
for Linq to SQL to track the changes. Much like people use
Interceptors in Hibernate.
The thing that concerns me with
this is the reliability issue. While an audit log on the ORM layer may
record everything that happens via code, it won't log any changes if
say a someone manually issues an SQL statement against the database,
or a hacker etc. Basically the information I'm dealing with is
somewhat sensitive. That's
|How to build a change tracking system - not audit system|
I have a requirement in which I need to capture data changes (not
auditing) and life cycle states on inventory.
Jave, Oracle, Hibernate + JPA
the data changes, we have been given a list of data elements that are
to be monitored. If the element changes we are to notify a given 3rd
party vendor. What I want to do is make this a generic service that
we can provide to any of our current and future 3rd party
We don't care who made the change or what the new
value is just that it changed.
The thought is that the
data layer of our application would use annotation on each of the data
|Change Data Capture or Change Tracking - Same as Traditional Audit Trail Table?|
Before I delve into the abyss of Microsoft documentation any
deeper, I'd like to know if someone experienced with Change Data
Capture and Change Tracking know if one or both of these can be used
to replace the traditional ...
"Audit trail table copy
of the 'real
table' (all of the fields of the original
plus date/time, user ID, and DML
inserted into by
... setup for a database
table audit trail, where the trigger populates the audit trail table
(which is all manual work).
The MSDN overview
documentation explains at a high level what Change Data Capture
|SQL Server 2008 change data capture vs triggers in audit trail|
We have audit trail implemented using triggers on our web
application. Those triggers log field level updates. So, in a table,
if you have 5 column values changed, we have 5 records in the audit
trail one for each column with old value and the new value.
Recently we have upgraded to SQL Server 2008. I have been
thinking of using the new change data capture feature as it gives a
very neat row level update with very less efforts and it's super-easy
to implement. Just wanted to get some opinions from people who have
been using change tracking for any caveat or any other real-world
useful info on this.
Any advice would be helpful.
|Store multiple data into one primary ID in mysql (audit trail)|
I thought i was in the right track. I forgot that a
user can do multiple activities. What I did was it's only one
activity. What can i do with this? I came up with a solution that
might work, come up with an sql statement that updates the activity
column without overwriting the text. But that seems stupid. Pretty
sure theres a better solution?
|Using a natural key, or using surrogate keys and audit table(s) for auditing/change log|
My first question on here so be nice!
I am a junior
developer with not much experience and am having trouble with this
I have a table which needs to be auditable. Let's
say this table records phone calls made by a call centre (it's not,
but it's just an example). I'll call it "CallHistory".
had originally planned to keep a separate table called "Callees" which
has the callees' name, phone number, etc. This table would be using a
surrogate primary key.
The CallHistory table would have a
foreign key to the Callee table.
I originally did this so
that if I changed a callee's phone nu