This blog promotes knowledge sharing through experience and collaboration. For more product information, visit our WebSphere Commerce CSE page. For easier navigation, utilize the Categories to find posts that match your interest.
Business Auditing Increases your Database Size
In this post I'd like to address an issue that can be easily be forgotten and can significantly impact the size of your WebSphere Commerce database, and possibly system performance.
Business Auditing can be performed for various reasons, for example, to review your marketing data updates, to monitor tasks performed in the administrative interfaces, or to monitor events in the store front.
However, after enabling Business Auditing, the BUSAUDIT table can grow very quickly. I have seen cases where this table constitutes more than 70% of the whole Commerce database. Depending on the auditing configuration, tens of thousands records can be created per day in the BUSAUDIT table.
Before enabling this feature, you should determine how long records need to be kept, whether historical records need to be archived, and define the process for archiving and deleting. You should not plan to keep all historical Business Audit records permanently in the BUSAUDIT table.
Archiving typically involves moving the records to another database or off-line storage. Once the records have been archived, they can be removed from the BUSAUDIT table.
You can use the DBClean utility to implement a clean up policy by creating a custom DBClean configuration for the BUSAUDIT table:
The actual number of days the records should stay in the BUSAUDIT table will vary, and will depend on your site's traffic and on your business requirements.
For a low traffic site, you might be able to keep the whole history in the table until it is deleted.
On the other hand, if you have a high traffic site and need to keep an archive of records for a long time, for example to be PCI compliant, you should consult your business team to determine exactly what needs to be archived.
This is just one part of keeping a healthy WebSphere Commerce database, for related information, please see the following links: