Why ibdata1 is still growing when I have used innodb_file_per_table in MySQL 5.1

Question

All my table in the db are created after I enabled the option "innodb_file_per_table", so I don't understand why ibdata1 is still growing from time to time, even with a very slow speed.

m.sr · Answer 1 · 2011-05-21T17:45:37.847

2

When you use file_per_table, it doesn't mean that ibdata* isn't used at all. There will still be stored "meta-data" for all your InnoDB tables ... Only the data itself goes to the other files

edited May 21 '11 at 17:45

answered May 21 '11 at 06:11

m.sr

1,060
1
8
19

score 1 · Accepted Answer · edited May 23 '17 at 12:41

I have the complete solution for how to clean up your innodb infrastructure permanently !!!

I actually solved this question long ago and had this accepted in StackOverflow. Please read this in its entirety, because I performed these steps for my company's clients dozens of times without incident. This will also keep ibdata1 as dirt small as possible. I guarantee it !!!

I also addressed this in a question in ServerFault.

Why ibdata1 is still growing when I have used innodb_file_per_table in MySQL 5.1

2 Answers2