I can understand that in some cases, but considering the "repair" command is one step manual process anyway, I don't see it needing to go that far.
Besides, the root of the question was how can the need for repair be detected other than a human noticing something isn't working on the frontend? Automated repair was a possible option, but automated problem state notification is better. From: [email protected] [mailto:[email protected]] On Behalf Of Simon Holywell Sent: Thursday, 5 August 2010 7:06 p.m. To: [email protected] Subject: Re: [phpug] MySQL automated maintenance/notifications Repairs should really be done by a DB Admin rather than in an automated way. On 5 August 2010 05:22, Aaron Cooper <[email protected]> wrote: Thanks Jochen, Does your cron script check for errors, or is it just running a Repair each time? A repair on each table seems to be rather intensive on the server even for just one DB. A ----- Original Message ----- From: Jochen Daum <mailto:[email protected]> To: [email protected] Sent: Thursday, August 05, 2010 1:20 PM Subject: Re: [phpug] MySQL automated maintenance/notifications Hi, of many sites we manage or host, only 2 of them get corruption of MySQL tables. It is easiest to either build a custom test script that runs with cron or buy a web monitoring service for the same purpose. If it involves notifying by text message, the web monitoring services appear always the easiest and cheapest way. Kind Regards, Jochen Daum Chief Automation Officer Automatem Ltd Phone: 09 630 3425 Mobile: 021 567 853 Email: [email protected] Skype: jochendaum Website: www.automatem.co.nz http://twitter.com/automatem http://nz.linkedin.com/in/automatem http://www.xing.com/go/invite/3425509.181107 http://www.aucklandbusinessnetworking.co.nz On Thu, Aug 5, 2010 at 1:16 PM, Aaron Cooper <[email protected]> wrote: Hi all, We just had a case where a table in a MySQL 5 database was "flagged as stopped" and needed to be repaired. We only discovered this as a certain segment of a site was not functioning correctly. Anyone care to share how they manage either: a) Automated maintenance/repair b) Automated notification of common MySQL table issues Cheers Aaron Error! Filename not specified. Error! Filename not specified. [email protected] mbl: +64 21 577 155 www.zanzomedia.com The information in this email or any attachment is confidential and may be legally privileged. It is intended solely for the intended recipient. Access to this email by anyone else is unauthorised. If you are not the intended recipient, any disclosure, copying, distribution or any action taken or omitted to be taken in reliance on it, is unauthorised and prohibited. Such action may breach copyright or otherwise be unlawful. If you have received this email in error, please delete and destroy all copies. -- NZ PHP Users Group: http://groups.google.com/group/nzphpug To post, send email to [email protected] To unsubscribe, send email to [email protected] <mailto:nzphpug%[email protected]> -- NZ PHP Users Group: http://groups.google.com/group/nzphpug To post, send email to [email protected] To unsubscribe, send email to [email protected] <mailto:nzphpug%[email protected]> -- NZ PHP Users Group: http://groups.google.com/group/nzphpug To post, send email to [email protected] To unsubscribe, send email to [email protected] <mailto:nzphpug%[email protected]> -- Simon Holywell http://www.simonholywell.com -- NZ PHP Users Group: http://groups.google.com/group/nzphpug To post, send email to [email protected] To unsubscribe, send email to [email protected] -- NZ PHP Users Group: http://groups.google.com/group/nzphpug To post, send email to [email protected] To unsubscribe, send email to [email protected]
