There is some impact from turning auditing on, but its advantages often outweigh the negatives. Consider the following points to get the maximum benefit:
- To prevent some very frequent updates from swamping the system, you can add the no_audit attribute to the dictionary entry of a field. A good candidate for this is the Last Login time element on the User table, which is very frequently updated.
- Never directly report on or even query the Audit table. Its size likely to be in several gigabytes. I have seen some instances getting overwhelmed with scripts that scan the Audit table, so don't do it! Use the History link instead.
- Don't try to change the contents of the Audit table. This is designed to be a permanent ...
