Greets fellow users, We have an RT 3.8.7 Deployment running on Centos with a MySQL backend.
The DB itself has grown quite large, currently around 300GB with 2.1 million tickets, this due to customers sending through images which is part of the ticket. About a year ago we partitioned the RT Database and that sped up things quite nicely however we're looking at further ways to improve speed. Is there any sort of archiving mechanism we can use so that the DB can run lighter? Regards Ronald