Re: How to deal with huge MYISAM corrupted table
Posted by: Rick James
Date: February 20, 2013 04:56PM

> For repairing purpose I used to stop the Mysql server on prod server & after that I moved the data directory to another server & started the Mysql server there with prod server's data directory.

That sounds like it adds risk.

If you have two machines, why not have Master-Slave. That way, you could failover while you are doing the repair?

Without knowing the cause of problem, there is no assurances that switching to InnoDB will be a cure. "Repair" situations are radically different with InnoDB. And "moving the data directory" is not as viable.

> we need to add primary key as some integer value?

If the table will never have more than 4 billion rows, then INT UNSIGNED is sufficient. Else BIGINT.

Options: ReplyQuote


Subject
Written By
Posted
Re: How to deal with huge MYISAM corrupted table
February 20, 2013 04:56PM


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.