Well, you can change the tables live and add the key constraints, etc. But I wonder if that doesn´t end up in desaster for some reason.
I would dump the database without the table structures, just the data. Empty the database, create the tables with the scripts from dbmail tar ball. Make sure they are created as innodb and everything else went fine, reimport that data, done. Greetings, Daniel Am 05.09.2011 um 11:20 schrieb Simon: > On Tue, Aug 30, 2011 at 7:58 PM, Igor Živković <[email protected]> wrote: >> On 08/29/2011 11:48 PM, Simon wrote: >> >> On 30/08/2011, at 9:42 AM, Reindl Harald wrote: >> >> your innodb-settings sucks >> >> this should not be so slow >> on our 15 GB dbmail-database "dbmail-util" needs only 5 minutes >> and there is normal access to anything while it tuns >> >> how much mameory has your box and what are your mysql-settings >> >> Thanks for the quick reply... i had thought it might be something like this. >> 2GB RAM on the MySQL box with the following: >> http://www.nzlocal.com/simon/mysqlconf.txt >> >> You can safely increase your innodb_buffer_pool_size to 1GB and >> innodb_log_file_size to 256MB. Just don't forget to check in MySQL >> documentation how it should be done once you already created a database. > > OK.. I was tearing my hair out (what little i have left) and did some > really basic checks of the tables..... > > THEY ARE MyISAM!!!! for some reason the instance of mysql does not > have the engine loaded and therefore the import that was completed a > month or so ago defaulted to MyISAM. > > So what the hell do i do now? nearly 80GB of DBmail tables that are in > MyISAM... I have no idea what todo. > > help. please :) > > Thanks > > Simon > _______________________________________________ > DBmail mailing list > [email protected] > http://mailman.fastxs.nl/cgi-bin/mailman/listinfo/dbmail _______________________________________________ DBmail mailing list [email protected] http://mailman.fastxs.nl/cgi-bin/mailman/listinfo/dbmail
