Database size is increasing while removing data from the table cmdb_rel_ci

[madhanrajesh]

"We are supposed to delete 10 lakh records per day (since we have 10Cr+ unwanted data) from the cmdb_rel_ci table, but this is generating a large number of entries in sys_audit_relation, sys_audit, and sys_audit_delete tables approximately 3 times the count of deleted records. Specifically, deleting a single record from cmdb_rel_ci results in 2 entries in sys_audit_relation, 1 entry in sys_audit, and 1 entry in sys_audit_delete. How can we optimize or prevent this excessive logging while performing deletions?"

[Dr Atul G- LNG]

Hi @madhanrajesh 

As the count is big, and the above solutions are not working better log a now support case, and the team can give you a more optimal solution.

[Sandeep90]

@madhanrajesh if the audit is not needed please disable BR on cmdb_rel_ci 'Audit Relationship Changes' to stop populating sys_audit table. Regarding other two tables please reach to support which can analyze use case and provide the instructions on how to disable populating those tables. 

[madhanrajesh]

hi sandeep

thanks for helping.,

we tried with, 

1. Used gr.setWorkflow(false);
2. Used gr.autoSysFields(false);
3. Disabled the "Audit Relationship Changes" Business Rule on cmdb_rel_ci
4. Cleared cache

However, we are still facing the same issue.

[Sandeep90]

Audit Relationship change will only help with not writing deletes to the sys_audit table, there are other properties that could be tweaked to stop writing to sys_audit_delete and sys_audit_relation table. Support should be equipped to provide those. 

[madhanrajesh]

Still, it's logging into the sys audit tables, any idea? @Sandeep90