|
|||||||||||
|
Re: InnoDB as storage engine for sa_bayes
From: Alex Woick <alex(at)wombaz.de>
Date: Wed Aug 29 2007 - 10:57:52 EDT
> -rw-rw---- 1 mysql mysql 264M Aug 27 17:09 awl.ibd > As you can see above, the new storage engine consumed 2 times Nothing to worry. But you have perhaps imported your data twice and have an empty ibdata1 file which only occupies space. I quoted the innodb data files. Since you have defined innodb_file_per_table, the table data is saved into the *.ibd files in the database directory. Without that option all table data would go to the ibdata* file(s) in the base data directory. As far as I know, data for one table is saved either in ibdata* or in the *.ibd file, but not both. Perhaps you played around and first imported the data without innodb_file_per_table, which imported into ibdata1. Then you perhaps dropped the tables and defined innodb_file_per table and imported again, so the *.ibd files were created and filled. The ibdata1 may now be empty, but it will never shrink. Try the following: Dump all databases which have innodb tables and drop all innodb tables. Stop the server, remove the ibdata1 and *.ibd files and restart the server. An empty and small ibdata1 file will be recreated. Now import your databases. I bet the ibdata1 file will not grow and all data will be imported into *.ibd. > It has exactly the same content like old database and it was It is not neccessary to dump/reload the data for changing the database engine of a table. Simply edit the tables with Mysql Query Browser or the Mysql Administrator and change the table engine from myisam to innodb. Or execute an SQL statement: "ALTER TABLE mytable ENGINE=innodb". Received on Wed Aug 29 10:58:30 2007 This archive was generated by hypermail 2.1.8 : Fri Oct 26 2007 - 03:16:51 EDT |
||||||||||
|
|||||||||||