From: Martin Gainty
Date: May 6 2011 12:20pm
Subject: RE: Input needed...
List-Archive: http://lists.mysql.com/mysql/224964
Message-Id: <BLU142-W27D7EE6F7FAFFB3FFCD8F1AE830@phx.gbl>
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="_c2301347-39fa-42c5-93b3-90ae6a325b8a_"

--_c2301347-39fa-42c5-93b3-90ae6a325b8a_
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable


> From: h.reindl@stripped
> To: mysql@stripped
> Subject: Re: Input needed...
>=20
> Am 06.05.2011 13:26=2C schrieb J M:
> > Config:
> >=20
> > Running on 8G Server.. Currently utilizing 7G.. running only mysql..
>=20
> > [mysqld]
> > innodb_data_home_dir =3D /var/lib/mysql/
> > innodb_data_file_path =3D ibdata1:2000M=3Bibdata2:10M:autoextend
>=20
> 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_pat=
h-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_inn=
odb_file_per_table
>=20
danke=2C
Martin
 		 	   		  =

--_c2301347-39fa-42c5-93b3-90ae6a325b8a_--