[rt-users] Help with mySQL query to prune RT3 database before upgrading to RT 4.2.5

[Alex Vandiver]

On 06/19/2014 12:56 PM, Lists wrote:
> I have a working copy of RT 3.8.1 on my test server including a copy of
> our current production database which is over 18 gig of old data.  I
> have imported this database into RT 4 and when I run make
> upgrade-database against the RT4 database, it runs a while and then dies
> with a message that the script was killed.

It would be extremely helpful to see the output of the failed upgrade.

> What I would like to be able to do before our "real" production upgrade
> is to wipeout everything from a given date back, including
> objects/attachments or anything associated with tickets older than 3
> years.  Our current production RT3 database, in all it's glory will be
> archived for posterity.  I was not the original admin of our RT system,
> so I am still on the learning curve and not completely familiar with all
> of the database tables and how they are linked.
> 
> Will RT:Shredder do this or do I need to use a custom mysql query to
> catch everything?

Shredder is the solution to removing data while preserving integrity,
but I would strongly advise instead determining and addressing what your
actual problem is.
 - Alex