Alternate solution : Do show table status on that database . In comment
field you can find info about corrupted table .
This will be faster than check table .
----- Original Message -----
From: "N.J. Thomas" <njt@stripped>
Sent: Tuesday, January 10, 2006 9:00 PM
Subject: checking for corruption?
> After a power outage, we had a large table (~2GiB, 23e6 records) get
> corrupted. Only a few rows were actually affected, so nobody noticed for
> a few weeks though. A repair fixed the problem.
> We are now considering running the "check table" command regularly
> (every 15 minutes?) and plugging that into our monitoring system, i.e.
> if "check table" reports an error, our script beeps/emails someone.
> My question is this: is it okay to run "check table" frequently? What
> impact will it have on production systems? How quickly will it check
> very large tables? Is there an alternative (better) solution?
> N.J. Thomas
> Etiamsi occiderit me, in ipso sperabo
> MySQL General Mailing List
> For list archives: http://lists.mysql.com/mysql
> To unsubscribe: http://lists.mysql.com/mysql?unsub=1