Hi,
We've ingested over 5000 packages via Archivematica and over time the MCP database has grown considerably. This slows performance when loading the transfer and ingest tabs, especially following a server restart. It doesn't seem to be a problem when actually running an ingest, but it may be a source of future problems that just aren't visible yet.
Is there a way to clean up the database? As I understand it, the only data that needs to stay in the MCP database is data that relates to running the microservices (and maybe the FPR?). Data related to previous transfers/SIPs could be exported elsewhere. Or, if that data is included in the AIPs themselves, it may not be necessary to keep it at all.
Beyond that, is there a way to test the "health" of the database? Given that the database generally seems to be modified during each upgrade, it would be helpful to be able to analyze it for potential problems.
Thanks,
Andrew