Cleanup in content_resource_delete

[Curtis Van Osch]

Good afternoon, 

We're running Sakai 19.4 and storing all resource content in the database. At the request of our DBAs, I'm working trying to reduce the size of our database. 

The first action we've identified is deleting the content of the Trash in resources. As we've neglected to run the Quartz cleanup job it's gotten quite large and needs to be taken care of. 

I was going to simply delete all the content in CONTENT_RESOURCE_DELETE and CONTENT_RESOURCE_BB_DELETE for anything with a DELETE_DATE > 30 days ago, which is what the job seems to do by default. 

However, I've been surprised during testing to see that deleted resources seem to still be in CONTENT_RESOURCE_BODY_BINARY with the same RESOURCE_ID, and remain so even after the cleanup job or deleting from trash ! 

Is that expected behaviour ? I assumed that content binaries were moved to the CONTENT_RESOURCE_BB_DELETE table upon deletion, but they seem to be duplicated. At least in our instance, maybe there is a config for that ? 

I'm worried that if I go ahead, we won't be able to identify the content that has been deleted but still exists in CONTENT_RESOURCE_BODY_BINARY. Should I delete the entries in that table before removing them from the two "DELETE" tables ?

I don't see anything on Jira that would be relevant.

Thanks for any insight you can provide, 

Curtis

Curtis Van Osch, B.A.Sc. Analyste en conception logiciel multiplateformes Livraison des services TI Enseignement, Pédagogie, Recherche et Expérience Étudiante

3000, chemin de la Côte‑Sainte‑Catherine Montréal (Québec)  H3T 2A7 514-340-6000, extension 2029