List:General Discussion« Previous MessageNext Message »
From:Brent Baisley Date:May 23 2007 3:43pm
Subject:Re: corruption in db. myisam bad? innodb good?
View as plain text  
You would need to find out the reason for the crash to prevent or minimize it. The reason
may be external to mysql.
Innodb can get really, really slow when tables get physically large if you don't have a
similar amount of RAM.
MyISAM doesn't support transactions, so no, that wouldn't help.

If you want to test Innodb as the table type, setup a replication/slave server with the
tables as Innodb instead. See how your 
queries run against it. The table structure needs to match on a replication/salev server,
not the table type. You can also make the 
slave the master in the event of a crash.

----- Original Message ----- 
From: "tim h" <timh@stripped>
To: <mysql@stripped>
Sent: Tuesday, May 22, 2007 2:56 PM
Subject: corruption in db. myisam bad? innodb good?

> hi. database is myisam,  5.8Gb, 7mil records.
> recently had some corruption i think due to mysqld service failure.
> 10 tabes were crashed.
> question --
> how can i prevent or minimize this?
> Will switching to innodb help?
> Will converting all my queries to transactions help?
> thanks.
> -- 
> Tim H
> Berkeley, CA

corruption in db. myisam bad? innodb good?tim h22 May
  • Re: corruption in db. myisam bad? innodb good?Brent Baisley23 May