<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>The Pythian Blog &#187; myisam</title>
	<atom:link href="http://www.pythian.com/news/tag/myisam/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.pythian.com/news</link>
	<description>News and views from Pythian DBAs</description>
	<lastBuildDate>Fri, 10 Feb 2012 09:54:45 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.4</generator>
		<item>
		<title>Silent MyISAM Table Definition Changes and mysqldump</title>
		<link>http://www.pythian.com/news/22695/silent-myisam-table-definition-changes-and-mysqldump/</link>
		<comments>http://www.pythian.com/news/22695/silent-myisam-table-definition-changes-and-mysqldump/#comments</comments>
		<pubDate>Thu, 16 Jun 2011 21:02:40 +0000</pubDate>
		<dc:creator>Singer Wang</dc:creator>
				<category><![CDATA[Group Blog Posts]]></category>
		<category><![CDATA[MySQL]]></category>
		<category><![CDATA[Technical Blog]]></category>
		<category><![CDATA[myisam]]></category>
		<category><![CDATA[mysqldump]]></category>

		<guid isPermaLink="false">http://www.pythian.com/news/?p=22695</guid>
		<description><![CDATA[The other day while trying to move a schema from one MySQL server to another, I encountered a very odd issue. The schema to be moved contained both MyISAM and InnoDB tables, so the only option I had was to dump the schema using mysqldump on the source server and import it on the destination [...]]]></description>
		<wfw:commentRss>http://www.pythian.com/news/22695/silent-myisam-table-definition-changes-and-mysqldump/feed/</wfw:commentRss>
		<slash:comments>4</slash:comments>
		</item>
		<item>
		<title>Upgrade to MySQL 5.1.56 on an old Bacula server using 5.0.x and MyISAM tables</title>
		<link>http://www.pythian.com/news/23181/upgrade-to-mysql-5-1-56-on-an-old-bacula-server-using-5-0-x-and-myisam-tables/</link>
		<comments>http://www.pythian.com/news/23181/upgrade-to-mysql-5-1-56-on-an-old-bacula-server-using-5-0-x-and-myisam-tables/#comments</comments>
		<pubDate>Mon, 13 Jun 2011 14:45:57 +0000</pubDate>
		<dc:creator>mcormond</dc:creator>
				<category><![CDATA[Group Blog Posts]]></category>
		<category><![CDATA[MySQL]]></category>
		<category><![CDATA[SysAdmin]]></category>
		<category><![CDATA[Technical Blog]]></category>
		<category><![CDATA[Bacula]]></category>
		<category><![CDATA[myisam]]></category>
		<category><![CDATA[MySQL 5.1.56]]></category>

		<guid isPermaLink="false">http://www.pythian.com/news/?p=23181</guid>
		<description><![CDATA[Hello there, it&#8217;s me again, with another blog about a DBA situation that a typical Linux Administrator may find themselves in. In this blog, i&#8217;m going to review a recent MySQL upgrade I have done on one of the systems I am involved in administering. This is a real world example of an upgrade project, [...]]]></description>
		<wfw:commentRss>http://www.pythian.com/news/23181/upgrade-to-mysql-5-1-56-on-an-old-bacula-server-using-5-0-x-and-myisam-tables/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Enhancing performance in WordPress by moving from MyISAM to Innodb</title>
		<link>http://www.pythian.com/news/23117/enhancing-performance-in-wordpress-by-moving-from-myisam-to-innodb/</link>
		<comments>http://www.pythian.com/news/23117/enhancing-performance-in-wordpress-by-moving-from-myisam-to-innodb/#comments</comments>
		<pubDate>Mon, 30 May 2011 16:05:26 +0000</pubDate>
		<dc:creator>francisco bordenave</dc:creator>
				<category><![CDATA[Group Blog Posts]]></category>
		<category><![CDATA[MySQL]]></category>
		<category><![CDATA[Technical Blog]]></category>
		<category><![CDATA[InnoDB]]></category>
		<category><![CDATA[myisam]]></category>
		<category><![CDATA[wordpress]]></category>

		<guid isPermaLink="false">http://www.pythian.com/news/?p=23117</guid>
		<description><![CDATA[Recently I was dealing with some locking issues in databases supporting WordPress. For those who don&#8217;t know it yet WordPress is a really cool open source tool for easy blogging. This tool is really easy to install (just drag and dropping in your home directory) and making it really easy for you to get up [...]]]></description>
		<wfw:commentRss>http://www.pythian.com/news/23117/enhancing-performance-in-wordpress-by-moving-from-myisam-to-innodb/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>There is more than one way to do it&#8230;.</title>
		<link>http://www.pythian.com/news/4155/there-is-more-than-one-way-to-do-it/</link>
		<comments>http://www.pythian.com/news/4155/there-is-more-than-one-way-to-do-it/#comments</comments>
		<pubDate>Tue, 29 Sep 2009 00:21:45 +0000</pubDate>
		<dc:creator>Sheeri Cabral</dc:creator>
				<category><![CDATA[MySQL]]></category>
		<category><![CDATA[archive]]></category>
		<category><![CDATA[blackhole]]></category>
		<category><![CDATA[clustered index]]></category>
		<category><![CDATA[consulting]]></category>
		<category><![CDATA[InnoDB]]></category>
		<category><![CDATA[INSERT DELAYED]]></category>
		<category><![CDATA[myisam]]></category>
		<category><![CDATA[Pythian]]></category>

		<guid isPermaLink="false">http://www.pythian.com/news/?p=4155</guid>
		<description><![CDATA[I spent Friday examining the systems for a more traditional consulting gig (in case you did not know, Pythian has offered more traditional consulting and emergency services in addition to our remote DBA offering for our entire 12 year history). It is a familiar story to many people &#8212; the database performance was unacceptable. The [...]]]></description>
		<wfw:commentRss>http://www.pythian.com/news/4155/there-is-more-than-one-way-to-do-it/feed/</wfw:commentRss>
		<slash:comments>4</slash:comments>
		</item>
		<item>
		<title>Using the Sphinx Search Engine with MySQL</title>
		<link>http://www.pythian.com/news/3782/using-the-sphinx-search-engine-with-mysql/</link>
		<comments>http://www.pythian.com/news/3782/using-the-sphinx-search-engine-with-mysql/#comments</comments>
		<pubDate>Mon, 31 Aug 2009 21:49:19 +0000</pubDate>
		<dc:creator>Gerry Narvaja</dc:creator>
				<category><![CDATA[MySQL]]></category>
		<category><![CDATA[PostgreSQL]]></category>
		<category><![CDATA[bottlenecks]]></category>
		<category><![CDATA[Full Text Search]]></category>
		<category><![CDATA[myisam]]></category>
		<category><![CDATA[plugin]]></category>
		<category><![CDATA[Pythian]]></category>
		<category><![CDATA[search engine]]></category>
		<category><![CDATA[sphinx]]></category>
		<category><![CDATA[sphinx.conf]]></category>
		<category><![CDATA[sphinxse]]></category>

		<guid isPermaLink="false">http://www.pythian.com/news/?p=3782</guid>
		<description><![CDATA[MySQL Full Text Search Limitations Suppose you have a MyISAM table containing a column with a full text index. This table starts to grow to a significant size (millions of rows) and gets updated fairly frequently. Chances are that you&#8217;ll start to see some bottlenecks when accessing this table, since without row level locking, the [...]]]></description>
		<wfw:commentRss>http://www.pythian.com/news/3782/using-the-sphinx-search-engine-with-mysql/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>MySQL Schema Synchronization and GUI Tools</title>
		<link>http://www.pythian.com/news/1301/mysql-schema-synchronization-and-gui-tools/</link>
		<comments>http://www.pythian.com/news/1301/mysql-schema-synchronization-and-gui-tools/#comments</comments>
		<pubDate>Tue, 21 Oct 2008 20:22:10 +0000</pubDate>
		<dc:creator>Keith Murphy</dc:creator>
				<category><![CDATA[MySQL]]></category>
		<category><![CDATA[foreign keys]]></category>
		<category><![CDATA[GUI tools]]></category>
		<category><![CDATA[InnoDB]]></category>
		<category><![CDATA[myisam]]></category>
		<category><![CDATA[MySQL Workbench]]></category>
		<category><![CDATA[SQLyog]]></category>

		<guid isPermaLink="false">http://www.pythian.com/blogs/1301/mysql-schema-synchronization-and-gui-tools</guid>
		<description><![CDATA[Or, There is a Use for GUI Tools! Recently I was working on a problem for a customer. They are converting a server with two InnoDB data files to innodb_file_per_table: $ ls -l ibdata* -rwxr-xr-x  1 mysql  mysql  2.0G Oct 14 13:10 ibdata1 -rwxr-xr-x  1 mysql  mysql  350G Oct 14 13:10 ibdata2 I honestly don&#8217;t [...]]]></description>
		<wfw:commentRss>http://www.pythian.com/news/1301/mysql-schema-synchronization-and-gui-tools/feed/</wfw:commentRss>
		<slash:comments>7</slash:comments>
		</item>
		<item>
		<title>MySQL Back to Basics: Analyze, Check, Optimize, and Repair</title>
		<link>http://www.pythian.com/news/1114/mysql-back-to-basics-analyze-check-optimize-and-repair/</link>
		<comments>http://www.pythian.com/news/1114/mysql-back-to-basics-analyze-check-optimize-and-repair/#comments</comments>
		<pubDate>Fri, 25 Jul 2008 16:53:18 +0000</pubDate>
		<dc:creator>Nicklas Westerlund</dc:creator>
				<category><![CDATA[MySQL]]></category>
		<category><![CDATA[analyze]]></category>
		<category><![CDATA[basics]]></category>
		<category><![CDATA[check]]></category>
		<category><![CDATA[InnoDB]]></category>
		<category><![CDATA[myisam]]></category>
		<category><![CDATA[optimize]]></category>
		<category><![CDATA[repair]]></category>

		<guid isPermaLink="false">http://www.pythian.com/blogs/1114/mysql-back-to-basics-analyze-check-optimize-and-repair</guid>
		<description><![CDATA[It felt like the right time for us to look back at some useful commands for table maintenance that some of us may not have mastered as much as we might like to think. In my post about gathering index statistics, I referred to OPTIMIZE TABLE, ANALYZE TABLE, and REPAIR TABLE &#8212; but I never [...]]]></description>
		<wfw:commentRss>http://www.pythian.com/news/1114/mysql-back-to-basics-analyze-check-optimize-and-repair/feed/</wfw:commentRss>
		<slash:comments>4</slash:comments>
		</item>
		<item>
		<title>MyISAM Statistics Gathering</title>
		<link>http://www.pythian.com/news/1103/myisam-statistics-gatherings/</link>
		<comments>http://www.pythian.com/news/1103/myisam-statistics-gatherings/#comments</comments>
		<pubDate>Fri, 04 Jul 2008 19:14:02 +0000</pubDate>
		<dc:creator>Nicklas Westerlund</dc:creator>
				<category><![CDATA[MySQL]]></category>
		<category><![CDATA[indexes]]></category>
		<category><![CDATA[myisam]]></category>
		<category><![CDATA[statistics]]></category>

		<guid isPermaLink="false">http://www.pythian.com/blogs/1103/myisam-statistics-gatherings</guid>
		<description><![CDATA[So, how does one gather statistics on indexes? With InnoDB it&#8217;s one thing, with MyISAM it&#8217;s another thing. This post however, will focus on MyISAM. There are various ways, each having their own drawbacks and positive sides. What about ANALYZE TABLE? It&#8217;s great &#8212; very fast in InnoDB. But with MyISAM a lock occurs while [...]]]></description>
		<wfw:commentRss>http://www.pythian.com/news/1103/myisam-statistics-gatherings/feed/</wfw:commentRss>
		<slash:comments>4</slash:comments>
		</item>
	</channel>
</rss>

