Administering AuditMaster : Archive Disk Limit

Archive Disk Limit
The Common Settings section offers one settable value, Archive Disk Limit. By default, the value is –1, which means that the system does not monitor the total size of all archived files. If the value is greater than zero bytes, then the system retains only the most recent files for which the total size is less than or equal to this number of bytes and deletes the older files.
Caution Use of this setting may lead to unintentional loss of archived audit records. Be sure to consider the possible situations when it may be undesirable to delete archived files automatically.
Errors to Audit
The Errors to Audit section sets the Pervasive PSQL status codes to log as audit events.
After AuditMaster installation, the default settings are as follows:
Operations to Audit Globally
The Operations to Audit window offers the same type of settings as the Operations to Audit button in the Audit Configuration window.
The difference is that in Server Settings the options are global for any file selected in an audit configuration, and in the Audit Configuration window, the button allows you to set operations to audit for individual files.
At installation time, the AuditMaster defaults in this window include all operations except Read. If you select different options, they become the new defaults for any file you add to an audit configuration group. Operations to audit set for earlier added files are not affected unless you click the Apply to All Files button.
Finally, if any file is removed from a group and then added again, its operations to audit settings default to the current selections in this window.
For information on individual file settings, see Operations to Audit by File.
Note In a Pervasive PSQL database, when the client-side cache engine is turned on, the cache engine reads an entire database page after 8 consecutive reads in anticipation of more reads. The records in the database page read by the cache engine are not audited by the event handler on the server. If auditing requires that every read be captured, verify the setting is off. However, lack of engine caching can reduce database performance. The behavior occurs only when the threshold of 8 consecutive reads is reached. If 7 reads and then an update occurs, no caching occurs and all 7 reads are captured. In Pervasive PSQL Control Center, expand Local Client, right-click MicroKernel Router, and select Properties, then click Performance tuning to see the setting Use Cache Engine. By default, the setting is off.