<?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>Linux Admin Zone &#187; mysql</title>
	<atom:link href="http://linuxadminzone.com/tag/mysql/feed/" rel="self" type="application/rss+xml" />
	<link>http://linuxadminzone.com</link>
	<description>Adding more reasons to celebrate Open Source.</description>
	<lastBuildDate>Thu, 29 Jul 2010 17:25:24 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0</generator>
		<item>
		<title>Compile mysql 5.1 with innodb and optimize for heavy usage</title>
		<link>http://linuxadminzone.com/compile-mysql-5-1-with-innodb-and-optimize-for-heavy-usage/</link>
		<comments>http://linuxadminzone.com/compile-mysql-5-1-with-innodb-and-optimize-for-heavy-usage/#comments</comments>
		<pubDate>Wed, 21 Apr 2010 13:11:41 +0000</pubDate>
		<dc:creator>jagbir</dc:creator>
				<category><![CDATA[database]]></category>
		<category><![CDATA[mysql]]></category>

		<guid isPermaLink="false">http://linuxadminzone.com/?p=206</guid>
		<description><![CDATA[MySQL stopped default inclusion of InnoDB in latest 5.1.x, so if you need InnoDB, you have to compile it from source. I have done following steps in CentOS 5.4 server to compile MySQL and optimize it later for a heavy site: 1. Remove earlier installation of MySQL, if any and download source rpm from MySQL [...]]]></description>
		<wfw:commentRss>http://linuxadminzone.com/compile-mysql-5-1-with-innodb-and-optimize-for-heavy-usage/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>How to quickly convert mysql databases from MyISAM to InnoDB</title>
		<link>http://linuxadminzone.com/how-to-quickly-convert-mysql-databases-from-myisam-to-innodb/</link>
		<comments>http://linuxadminzone.com/how-to-quickly-convert-mysql-databases-from-myisam-to-innodb/#comments</comments>
		<pubDate>Sat, 10 Apr 2010 10:06:30 +0000</pubDate>
		<dc:creator>jagbir</dc:creator>
				<category><![CDATA[database]]></category>
		<category><![CDATA[mysql]]></category>

		<guid isPermaLink="false">http://linuxadminzone.com/?p=198</guid>
		<description><![CDATA[Recently I was in need to convert all databases of a MySQL server from MyISAM engine to InnoDB. They are facing severe issues due to table level locking in MyISAM and wanted move to InnoDB. This task can be a mammoth work but if you work little smarter, all you need to execute few statements [...]]]></description>
		<wfw:commentRss>http://linuxadminzone.com/how-to-quickly-convert-mysql-databases-from-myisam-to-innodb/feed/</wfw:commentRss>
		<slash:comments>5</slash:comments>
		</item>
		<item>
		<title>Find out the clients of your MySQL server</title>
		<link>http://linuxadminzone.com/find-out-the-clients-of-your-mysql-server/</link>
		<comments>http://linuxadminzone.com/find-out-the-clients-of-your-mysql-server/#comments</comments>
		<pubDate>Tue, 16 Mar 2010 08:49:58 +0000</pubDate>
		<dc:creator>jagbir</dc:creator>
				<category><![CDATA[database]]></category>
		<category><![CDATA[mysql]]></category>

		<guid isPermaLink="false">http://linuxadminzone.com/?p=181</guid>
		<description><![CDATA[Sometimes in large deployments, there are cases when MySQL server, setup by you long time back which has been in use by multiple teams in your organization, needs some change or update or intrupption in its service and you are in need to know how many clients are there which connects to this server. One [...]]]></description>
		<wfw:commentRss>http://linuxadminzone.com/find-out-the-clients-of-your-mysql-server/feed/</wfw:commentRss>
		<slash:comments>8</slash:comments>
		</item>
		<item>
		<title>Optimize MySQL on a Large Database Server</title>
		<link>http://linuxadminzone.com/optimize-mysql-on-a-large-database-server/</link>
		<comments>http://linuxadminzone.com/optimize-mysql-on-a-large-database-server/#comments</comments>
		<pubDate>Sat, 13 Dec 2008 06:13:29 +0000</pubDate>
		<dc:creator>jagbir</dc:creator>
				<category><![CDATA[database]]></category>
		<category><![CDATA[mysql]]></category>
		<category><![CDATA[optimization]]></category>

		<guid isPermaLink="false">http://linuxadminzone.com/?p=31</guid>
		<description><![CDATA[On a large server which run primarily mysql service only, the first step you should take is to copy the proper config file which is already optimized for large systems: # mv /etc/my.cnf/my.cnf_OLD # cp /usr/share/doc/mysql-server-5.0.44/my-huge.cnf /etc/my.cnf I&#8217;m using 5.0.44 version here on a CentOS 5.2 box. You need to adjust path as per your [...]]]></description>
		<wfw:commentRss>http://linuxadminzone.com/optimize-mysql-on-a-large-database-server/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Ignore mysql error while executing bulk statements</title>
		<link>http://linuxadminzone.com/ignore-mysql-error-while-executing-bulk-statements/</link>
		<comments>http://linuxadminzone.com/ignore-mysql-error-while-executing-bulk-statements/#comments</comments>
		<pubDate>Fri, 31 Oct 2008 11:25:25 +0000</pubDate>
		<dc:creator>jagbir</dc:creator>
				<category><![CDATA[database]]></category>
		<category><![CDATA[mysql]]></category>

		<guid isPermaLink="false">http://linuxadminzone.com/?p=27</guid>
		<description><![CDATA[Sometimes when running MySQL in batch mode, it requires to ignore some mysql errors which pops in between. As an example, we can consider a scenerio where thousands of inserts required to be done and the statements are saved in a file, suppose in indata.sql. But it may be the case that some records are [...]]]></description>
		<wfw:commentRss>http://linuxadminzone.com/ignore-mysql-error-while-executing-bulk-statements/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
	</channel>
</rss>
