Centrify

Tips for finding Knowledge Articles

  • - Enter just a few key words related to your question or problem
  • - Add Key words to refine your search as necessary
  • - Do not use punctuation
  • - Search is not case sensitive
  • - Avoid non-descriptive filler words like "how", "the", "what", etc.
  • - If you do not find what you are looking for the first time,reduce the number of key words you enter and try searching again.
  • - Minimum supported Internet Explorer version is IE9
Home  >
article

KB-7540: Cleaning up old session data from target AuditStore database

Auditing and Monitoring Service ,  

13 September,18 at 07:47 PM

Question:
Is it possible to clean up old sessions from an AuditStore database to free space?

Answer:
Please find attached to this article a .sql script: 'PurgeSessionsSQLJob - V2.sql' 
This script may be leveraged as a one-time use, or recurring job to clean up old session data from a target AuditStore.

The script should be run against the target AuditStore database as a DBA. Default behavior will remove sessions older than 365 days. This value can be modified on line #9 of the script.

Please also refer to KB-3394: Is it possible to purge audit sessions older than 'x' number of days for alternate/standalone mechanism for leveraging this tool. 
Attachments:
PurgeSessionsSQLJob - V2.sql

Still have questions? Click here to log a technical support case, or collaborate with your peers in Centrify's Online Community.

Related Articles

 articleKB-4018: DirectAudit Session logging (scp file stream content) can cause excessive DB usage articleKB-4168: How to make a previously active Audit Store database active again? articleKB-7555: Unable to login as root after upgrade to Centrify Suite 2016 (CDC 5.3.0) articleKB-2104: How to archive/delete DirectAudit data using SQL tools articleKB-7537: Unable to re-attach old AuditStore database articleKB-10203 How to rename DirectAudit Database? articleKB-3925: How to add Centrify parameter to a group policy articleKB-6041: How to show current license type in use by adclient articleKB-6040: How to change the license type in use after adclient successful joined to the AD?