Hi Dave,
MySQL has to convert each one of those attachments to the new datatype.
Sadly this just takes time. Our DB is only miniscule compared to yours and
from memory it takes around an 1hour just to get through all of our
attachments.
I think it is highly likely that this could be normal due
: Aaron Guise aa...@guise.net.nz
To: David Hobley david.hob...@mionegroup.com
Cc: rt-users@lists.bestpractical.com
Sent: Monday, 2 March, 2009 8:54:58 PM GMT +10:00 Brisbane
Subject: Re: [rt-users] DB Problems upgrading to RT 3.8.2 from 3.6.5
Hi Dave,
MySQL has to convert each one of those
On Tue, Mar 03, 2009 at 08:23:31AM +1000, David Hobley wrote:
If that is the case, then RT is un-upgradeable. Which would be a problem
obviously. I can't take out our database for 6 days. Over a weekend, sure.
But no more than that. Does anyone have any suggestions as to how I can
Message -
From: Jesse Vincent je...@bestpractical.com
To: David Hobley david.hob...@mionegroup.com
Cc: rt-users@lists.bestpractical.com
Sent: Tuesday, 3 March, 2009 8:34:27 AM GMT +10:00 Brisbane
Subject: Re: [rt-users] DB Problems upgrading to RT 3.8.2 from 3.6.5
On Tue, Mar 03, 2009
Hello,
I have a (happily) running RT 3.6.5 with approx 300,000 tickets in it and a
database of size of around 9 Gig (lots of attachments sadly). I have the
application upgraded, but when I try and run the schema upgrade in my test
environment it is taking forever (for values of forever which
