File per table is required if you want to implement compression via the
barracuda file format.
On 3 Oct 2011 06:39, "Adarsh Sharma" wrote:
> innnodb_file per table creates ibdata files for each table and What to
> do if some tables data are deleted frequently.
> I have a innodb table which was tru
innnodb_file per table creates ibdata files for each table and What to
do if some tables data are deleted frequently.
I have a innodb table which was truncated after 150GB in mysql database.
Reindl Harald wrote:
Am 02.10.2011 22:10, schrieb Dhaval Jaiswal:
Hi All,
How to shrink the Mysql
Thanks to all for your detailed info.
Hope Mysql community will add some solution for this in new release as to we
moved from MyISAM to InooDB for performance purpose.
On Mon, Oct 3, 2011 at 2:00 AM, Reindl Harald wrote:
> yes and after that you can do "optimize table" like for MYISAM
> "ibdata
yes and after that you can do "optimize table" like for MYISAM
"ibdata1", "ib_logfile0", "ib_logfile1" will still exists and
MUST NOT be removed but "ibdata1" will not grow endless
i do not know "other benefits" but they are enough
on the other hand - what are the benefits of having a dumb large
Currently in my database only 5 tables are of innodb engine.
"innodb_file_per_table" will create each file per table is it ? what are the
other benefits of it.
If so than again i have to follow the dump & restore procedure.
On Mon, Oct 3, 2011 at 1:50 AM, Reindl Harald wrote:
>
>
> Am 02.10.2
Am 02.10.2011 22:10, schrieb Dhaval Jaiswal:
> Hi All,
>
> How to shrink the Mysql ibdata1 files.
>
> The actual size of database is only hardly 10G, but ibdata1 is showing 73G
> full. I did some googling and found the following procedure.
>
> Do a mysqldump of all databases, procedures, t
