MySQL Forums
Forum List  »  InnoDB

Switch to file_per_table using a slave
Posted by: Chris Weyn
Date: May 07, 2010 01:18PM

I was wondering if anybody had gone through the process of going from shared tablespace to file_per_table using a temporary slave. I cannot afford too much down time on my database and the shared tablespace is ~250Gb. I was thinking of hanging a slave onto the database, setting up the slave with file_per_table, building it up from a mysqldump of the master, and letting it catch up. Once caught up, I stop both databases and do a binary copy of the resulting files to the master and re-start the master after having made the adequate changes in my.cnf.

Anything drastically wrong with this scenario? If anybody has gone through this, could they please share any hurdles they had to overcome?

Thank you,


Options: ReplyQuote

Written By
Switch to file_per_table using a slave
May 07, 2010 01:18PM

Sorry, you can't reply to this topic. It has been closed.

Content reproduced on this site is the property of the respective copyright holders. It is not reviewed in advance by Oracle and does not necessarily represent the opinion of Oracle or any other party.