<html><head><style type='text/css'>p { margin: 0; }</style></head><body><div style='font-family: Times New Roman; font-size: 12pt; color: #000000'>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 optimise this at all?<br><br>Cheers,<br>David<br>----- Original Message -----<br>From: "Aaron Guise" <aaron@guise.net.nz><br>To: "David Hobley" <david.hobley@mionegroup.com><br>Cc: rt-users@lists.bestpractical.com<br>Sent: Monday, 2 March, 2009 8:54:58 PM GMT +10:00 Brisbane<br>Subject: Re: [rt-users] DB Problems upgrading to RT 3.8.2 from 3.6.5<br><br>Hi Dave, <br><br>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. <br>
<br>I think it is highly likely that this could be normal due to the amount of data it has to manipulate. But as it said in the docs you need to test everything. especially those binary attachments namely .pdf,.xls etc. I have some difficulty with my database for some reason or another where in doing the schema upgrade it proceeds to corrupt them all....<br>
<br>--<br>Regards <br><br>Aaron<br><br><div class="gmail_quote">On Mon, Mar 2, 2009 at 2:16 PM, David Hobley <span dir="ltr"><<a href="mailto:david.hobley@mionegroup.com" target="_blank">david.hobley@mionegroup.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><div><div style="font-family: Times New Roman; font-size: 12pt; color: rgb(0, 0, 0);">Hello,<br>
<br>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 equate to around 6 days anyway):<br>
<br># perl etc/upgrade/<a href="http://schema.mysql-4.0-4.1.pl" target="_blank">schema.mysql-4.0-4.1.pl</a> rt3 root "password > ~/sql.queries<br># time `mysql -p rt3 < ~/sql.queries`<br>Enter password: <br><br>
real 8727m23.622s<br>user 0m0.012s<br>sys 0m0.004s<br><br>Does anyone have any suggestions as to how I can make this faster? I have tried to optimise MySQL as much as possible, but I am not a db expert and obviously there is something wrong. Nb. The test environment is actually more powerful than the production one after having shutdown evey VM on the machine and ensured I was only running this for the time it took.<br>
-- <br>Cheers,<br><font color="#888888">David <br><br></font></div></div><br>_______________________________________________<br>
<a href="http://lists.bestpractical.com/cgi-bin/mailman/listinfo/rt-users" target="_blank">http://lists.bestpractical.com/cgi-bin/mailman/listinfo/rt-users</a><br>
<br>
Community help: <a href="http://wiki.bestpractical.com" target="_blank">http://wiki.bestpractical.com</a><br>
Commercial support: <a href="mailto:sales@bestpractical.com" target="_blank">sales@bestpractical.com</a><br>
<br>
<br>
Discover RT's hidden secrets with RT Essentials from O'Reilly Media.<br>
Buy a copy at <a href="http://rtbook.bestpractical.com" target="_blank">http://rtbook.bestpractical.com</a><br></blockquote></div><br>
<br><br>-- <br>Cheers,<br>David Hobley<br><br>IT Manager<br>Creators of Miessence, MiVitality and MiEnviron<br><br>Phone: +61 (7) 5582 7020<br>Fax: +61 (7) 5539 6719<br>USA Fax 1800 840 0827<br>Email : david.hobley@mionegroup.com<br>Website: www.mionegroup.com<br><br><br></div></body></html>