What does cert_element table store ? Can cert_element and cert_audit_result tables be safely truncated ?Summary<!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: #000000; } span { font-size: 12pt; font-family: Lato; color: #000000; } h2 { font-size: 24pt; font-family: Lato; color: black; } h3 { font-size: 18pt; font-family: Lato; color: black; } h4 { font-size: 14pt; font-family: Lato; color: black; } a { font-size: 12pt; font-family: Lato; color: #00718F; } a:hover { font-size: 12pt; color: #024F69; } a:target { font-size: 12pt; color: #032D42; } a:visited { font-size: 12pt; color: #00718f; } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: block; max-width: ; width: auto; height: auto; } } cert_element is the mapping of a column in a specific record to whether or not it is certified and the date/time/user that certified it. For example, if the user was certifying the cmdb_ci_computer "owned by" column, it would create a record for every CI in cmdb_ci_computer with "owned by" as the element needing to be certified, and awaiting customer audit manager to certify that column for those CIs. Note: Truncating table cert_element will cause a loss in any previously certified items. So if there is a need to save previous audits, this will need to be considered.cert_audit_result can be safely truncated using gs.truncateTable("cert_audit_result ") from background scripts with "global" scope; Note: Make sure “Record for rollback” is NOT selected in background scripts while executing gs.truncateTable. Recording for rollback creates a shadow table and the data is copied to shadow table before truncation happens, and for large tables the environment can run out of resources .