Auditing SQL Server data changes -


I am changing our auditing process for our SQL Server 2005 database and I came back to change data capture in SQL Server 2008. I am

It looks like a good idea, and I am trying to do it, but before I have used it in any commercial environment and what are your thoughts?

I saw when I was reading CDC in MD Support, he said that usually audit data will be kept for a few days. It is not possible, I would like to keep the data indefinitely, does anyone know of problems from this point of view?

If this is not a good solution for unknown reasons, then do you have any other solution for auditing data changes? I'm eager to use a system that gives me any table Can be implemented in the board.

I am after the origin: "before, after, by whom, when" information for any change

In my opinion, the CDC should be the only means of termination. I have implemented audit trail solutions in the past and they have included in the use of triggers, it is highly messy and excessive The database has become an intense demonstration.

What does the CDC give you the ability to log audit data without the use of triggers, but you still need methods to take that data into a permanent table for each table The mirror table can be done with audit or a table that tracks all the changes in all the tables (I have done later).

Here are some links: Additional information about using triggers:

Here's an open source audit tracking solution That uses LINQ:


Comments

Popular posts from this blog

python - Overriding the save method in Django ModelForm -

html - CSS autoheight, but fit content to height of div -

qt - How to prevent QAudioInput from automatically boosting the master volume to 100%? -