bothering you once more…
Loking at an RT system that has grown for several years, I found that
most tickets aren’t being looked at anymore when they’re older than,
say, one year or so. But these tickets are still in the database, have
to be indexed and cause the DB to slow down over time.
I thought of “moving” tickets older than a certain age off to a
read-only “archive” database that’s running on a separate machine, with
a separate web server etc. For the case that a ticket isn’t found in the
"current" RT environment, a link to the archive could easily be added to
the templates. This should do for most situations.
Any caveats? Is there a clean way to do this via the RT API?