Hi,
One of our sites is high traffic and unfortunately it is built with Cobalt 8. The database is so huge the site barely runs, in total it's 3.45gb - largely it seems due to the size of the js_res_audit_log table - why causes this to be so huge? Is there a way to stop it becoming to massive.
I have deleted records in that table and the js_res_hits tables that were older than 1 day.
This alone has reduced the db size from 3.45gb to 190mb. There were over 5 million rows in the js_res_audit_log table...
How can I stop this from happening again?
Thanks
Hi,
One of our sites is high traffic and unfortunately it is built with Cobalt 8. The database is so huge the site barely runs, in total it's 3.45gb - largely it seems due to the size of the js_res_audit_log table - why causes this to be so huge? Is there a way to stop it becoming to massive.
I have deleted records in that table and the js_res_hits tables that were older than 1 day.
This alone has reduced the db size from 3.45gb to 190mb. There were over 5 million rows in the js_res_audit_log table...
How can I stop this from happening again?
Thanks