Comments on: MySQL Back to Basics: Analyze, Check, Optimize, and Repair http://www.pythian.com/news/1114/mysql-back-to-basics-analyze-check-optimize-and-repair/ News and views from Pythian DBAs Sat, 20 Mar 2010 20:27:09 +0000 http://wordpress.org/?v=2.8.4 hourly 1 By: Artículos destacados de Julio | cambrico.net http://www.pythian.com/news/1114/mysql-back-to-basics-analyze-check-optimize-and-repair/#comment-253100 Artículos destacados de Julio | cambrico.net Wed, 06 Aug 2008 19:30:57 +0000 http://www.pythian.com/blogs/1114/mysql-back-to-basics-analyze-check-optimize-and-repair#comment-253100 [...] Check, Optimize, y Repair bien explicados por los "maestros" de Pythian Group (en [...] [...] Check, Optimize, y Repair bien explicados por los “maestros” de Pythian Group (en [...]

]]> By: Rounding Up The Remaining Database Posts | Mats Lindh http://www.pythian.com/news/1114/mysql-back-to-basics-analyze-check-optimize-and-repair/#comment-248924 Rounding Up The Remaining Database Posts | Mats Lindh Fri, 01 Aug 2008 19:21:07 +0000 http://www.pythian.com/blogs/1114/mysql-back-to-basics-analyze-check-optimize-and-repair#comment-248924 [...] Westerlund has a post about MySQL Back to Basics: Analyze, Check, Optimize, and Repair on the pythian blog, featuring a overview of the useful - and abused - methods of rescuing and [...] [...] Westerlund has a post about MySQL Back to Basics: Analyze, Check, Optimize, and Repair on the pythian blog, featuring a overview of the useful – and abused – methods of rescuing and [...]

]]> By: Nicklas Westerlund http://www.pythian.com/news/1114/mysql-back-to-basics-analyze-check-optimize-and-repair/#comment-243851 Nicklas Westerlund Fri, 25 Jul 2008 21:48:20 +0000 http://www.pythian.com/blogs/1114/mysql-back-to-basics-analyze-check-optimize-and-repair#comment-243851 Ryan, indeed - and unfortunately it's very widely spread among small to midsized companies that I've seen so far.. There's a common belief that "OPTIMIZE" can be ran as often as they want to, without problems, and that it will magically improve things, even if they ran it an hour ago. This is, however, specific to each company, and is not a general comment, but merely something I've observed.. Ryan, indeed – and unfortunately it’s very widely spread among small to midsized companies that I’ve seen so far.. There’s a common belief that “OPTIMIZE” can be ran as often as they want to, without problems, and that it will magically improve things, even if they ran it an hour ago.

This is, however, specific to each company, and is not a general comment, but merely something I’ve observed..

]]> By: Ryan Lowe http://www.pythian.com/news/1114/mysql-back-to-basics-analyze-check-optimize-and-repair/#comment-243810 Ryan Lowe Fri, 25 Jul 2008 20:01:27 +0000 http://www.pythian.com/blogs/1114/mysql-back-to-basics-analyze-check-optimize-and-repair#comment-243810 I think your statement about OPTIMIZE being " ... often overrated and used more often than necessary." is dead-on. For MyISAM tables, one can check the Data_free column from the output of "SHOW TABLE STATUS LIKE '%table%'\G" to see if it is even necessary to run OPTIMIZE. I think your statement about OPTIMIZE being ” … often overrated and used more often than necessary.” is dead-on. For MyISAM tables, one can check the Data_free column from the output of “SHOW TABLE STATUS LIKE ‘%table%’\G” to see if it is even necessary to run OPTIMIZE.

]]>