Timeline for Migrate from innodb_file_per_table to off in MySQL
Current License: CC BY-SA 3.0
8 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jan 16, 2015 at 19:11 | history | edited | RolandoMySQLDBA | CC BY-SA 3.0 |
added 6 characters in body
|
| Dec 7, 2014 at 23:03 | comment | added | Matija Nalis | @RolandoMySQLDBA my bad, premature "enter" commited comment before I copy/pasted (hopefully more useful) mysql options - not necessarily for the original poster (who hopefully solved his problem by now), but for other people with similar problems which may come upon the question in the future. | |
| Dec 7, 2014 at 22:59 | comment | added | Matija Nalis |
You can also split ConvertInnoDBToInnoDB.sql to many smaller chunks and run them one by one if you like. As for performance, you could alternatively play with open_files_limit, table_open_cache, table_definition_cache, innodb_open_files -- but still preferably on test server
|
|
| Dec 7, 2014 at 22:55 | comment | added | RolandoMySQLDBA | @MatijaNalis please notice that Justin asked this question 9 months ago. He would already have done this. | |
| Dec 7, 2014 at 22:53 | comment | added | Matija Nalis | @Justin, so, make a test server, restore mysqldump on that, and try it there before doing same to production? | |
| Mar 21, 2014 at 1:37 | vote | accept | Justin | ||
| Mar 19, 2014 at 3:54 | comment | added | Justin |
Thanks, a little worried about running this on production with over 2,500 databases and 30,000 tables. Not even sure if this is going to help with our root problem. In fact, going to a single ibdata file may degrade performance further instead of improve it. Thoughts?
|
|
| Mar 18, 2014 at 3:34 | history | answered | RolandoMySQLDBA | CC BY-SA 3.0 |