> From: h.rei...@thelounge.net
> To: mysql@lists.mysql.com
> Subject: Re: Input needed...
> 
> Am 06.05.2011 13:26, schrieb J M:
> > Config:
> > 
> > Running on 8G Server.. Currently utilizing 7G.. running only mysql..
> 
> > [mysqld]
> > innodb_data_home_dir = /var/lib/mysql/
> > innodb_data_file_path = ibdata1:2000M;ibdata2:10M:autoextend
> 
> bad - you get one flat storage-pool which will grow
> and never can be rudced with "optimize table"
MG>so the datafile could never be reduced with OPTIMIZE TABLE
MG>http://www.pythian.com/news/1067/difference-between-innodb_data_file_path-and-innodb_file_per_table/
MG>would you suggest using innodb_file_per_table for more granular control?
MG>is it worth the effort to export the database and reimport the data into new 
db using innodb_file_per_table enabled in my.cnf?
MG>http://dev.mysql.com/doc/refman/5.1/en/innodb-parameters.html#sysvar_innodb_file_per_table
> 
danke,
Martin
                                          

Reply via email to