Hi Travis, On Wed, Sep 08, 2004 at 10:42:09AM -0700, Travis Murdock wrote:
Our OTRS database has grown to over 1.5 GB. We are eager to trim it down without losing the tickets. Many of our tickets have very large attachments that we don't need anymore. We would like to delete the attachments on tickets that are more than 90 days old, but keep the tickets themselves. This change would allow our customers to respond to old tickets and allow us to see the history, without saving the unnecessary attachments.
We have attempted to do this a couple of times, but each time we end up deleting the tickets or losing other data inside the tickets.
Is there a prescribed way to complete this task?
Is there another way to significantly reduce the database size without losing the data?
If you use the database backend for your attachments, the the attachments stored in article_attachment table. In this table is also a create_time column. So you can just delete attachments older then... by using SQL link "DELETE FROM article_attachment WHERE create_time ...". PS: In my opinion, it's always good to have the attachments longer. Maybe a few years. So I would use the filesystem backend, the the attachments are stored in the file system and normally the file system is big enough. Read more: http://doc.otrs.org/1.2/en/html/performance-tuning.html#PERFORMANCE-TUNING-O...
Travis Murdock
Cloudmark
Martin Edenhofer -- ((otrs.de)) :: OTRS GmbH :: Norsk-Data-Str. 1 :: 61352 Bad Homburg http://www.otrs.de/ :: Manage your communication!