Audit Trail Scope
I am unable to implement Audit Trail due to the performance implications associated with auditing my entire server. Being able to audit very specific attributes, elements, or trees would allow me to take advantage of the Audit Trail feature in a practical way.
I want the ability to audit attribute changes with the following details:
* old value
* new value
* timestamp
* user
Jake Messner
shared this idea
We have implemented additional filtering capability in the AF Audit Trail in recent releases. Please have a look and let us know if it’s sufficient for your needs.
Regarding AF Audit Trail for individual databases, we currently do not have any plans to implement that idea.
-
Roger Palmen
commented
I ran into similar issues (space usage) using the audit trail. I also would like to limit the scope, but i would be helped quite much if i could limit the audit trail to one or more AF databases.
And if the CDC does not support the limitations, you can also create the Audit Trail and then prune the Audit Trail for the unwanted entries. Less then ideal i agree, but that would be a stop-gap approach.
-
The auditing feature in the AF Server is implemented with SQL Server Changed Data Capture (CDC), which is designed to capture all changes. With this implementation, there's not a good way to only capture changes to specific attributes, elements or trees. In addition, an element spans multiple tables so that adds more complexity.