You can fix the problem with the database file size by setting innodb_file_per_table option in your mysql config file. Instead of one large file, it will tell the database engine to split the entire database into smaller files, one file per table. This makes database maintenance, optimization and backups much easier and increases performance, especially on machines with not enough RAM to keep the entire DB cached in memory. As far as I remember, after switching to innodb_file_per_table you have to do ALTER TABLE (or OPTIMIZE, but for InnoDB it's mapped to ALTER anyway) for each InnoDB table to make it 'jump out' from the ibdata to a separate file. It won't make the ibdata file smaller however, but the file won't be used anymore.
/TJM On Mon, 19 Oct 2009 21:56:05 -0700 (PDT) Kunsheng Chen <[email protected]> wrote: >Mysql in my project is getting huge because of that >'ibdata1' file. > >I am thinking of backup databases and restore after >delete 'ibdata1'. > >Recall I did tell the ./make_project script the mysql >user name and password when created the project long time >ago. > >I am wondering if a backup of the project database is >enough for that ? > >Also my file 'ibdata1' is getting too huge (16GB), it was >caused by some innodb settings. The thing I am worried is >that after deleting ibdata1 and restart, it will getting >back to that size again. > > >Any idea ? > > >Thanks, > >-Kun > > > >_______________________________________________ >boinc_dev mailing list >[email protected] >http://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev >To unsubscribe, visit the above URL and >(near bottom of page) enter your email address. _______________________________________________ boinc_dev mailing list [email protected] http://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev To unsubscribe, visit the above URL and (near bottom of page) enter your email address.
