1 of 1 people found this helpful
Unfortunately, AF audit can only be enabled and cannot be set to record specific information.
Thanks for your reply. Just another few questions:
- Can AF audit, if active, affect performace on PI Server?
- So, is reccomended turn on AF audit on production environment H24?
The AF audit (if i'm not mistaken) mainly impacts the SQLserver used to store the PIFD AF database. So there is no impact on the PI Data Archive, and as far as i know little to no impact on the AF server.
If not needed, then you should not turn it on. But if it is needed, you should consider the impact on sizing and performance, mainly on the SQLserver side. The audit trail takes performance to upkeep, and storage. Growth is dependant on the volume of changes on the AFmodel. Typically, i've only seen a requirement for audit logging in regulated environments (food, pharmaceuticals, etc.)
Thanks a lot for your help
Have a nice day!
You are correct that AF Audit trail will affect performance of the SQL Server instance used by AF but not the PI Data Archive. None of the audit data generated by AF is sent to the PI Data Archive. AF (v2.6) Audit Trail uses the Change Data Capture (CDC) feature of SQL Server Enterprise Edition. Since the use of CDC causes additional data to get written to the disk, there is some impact on disk IO workload.
There is no free lunch when it comes to physics (and hard disks).