<?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>Pablowe &#187; MySQL</title>
	<atom:link href="http://www.pablowe.net/tag/mysql/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.pablowe.net</link>
	<description>%&#62; random tech;</description>
	<lastBuildDate>Mon, 21 Jun 2010 21:32:12 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.1</generator>
		<item>
		<title>PCI DSS &amp; MySQL &#8211; Requirement 6</title>
		<link>http://www.pablowe.net/2010/04/pci-dss-mysql-requirement-6/</link>
		<comments>http://www.pablowe.net/2010/04/pci-dss-mysql-requirement-6/#comments</comments>
		<pubDate>Wed, 07 Apr 2010 22:35:22 +0000</pubDate>
		<dc:creator>rlowe</dc:creator>
				<category><![CDATA[MySQL]]></category>
		<category><![CDATA[MySQL Administration]]></category>
		<category><![CDATA[PCI DSS]]></category>
		<category><![CDATA[Security]]></category>
		<category><![CDATA[MySQL Security]]></category>

		<guid isPermaLink="false">http://www.pablowe.net/?p=527</guid>
		<description><![CDATA[Requirement 6 of PCI DSS v1.2 states that in order to be compliant, an organization must: &#8220;Develop and maintain secure systems and applications&#8221; &#8220;Unscrupulous individuals use security vulnerabilities to gain privileged access to systems. Many of these vulnerabilities are fixed by vendor- provided security patches, which must be installed by the entities that manage the [...]]]></description>
		<wfw:commentRss>http://www.pablowe.net/2010/04/pci-dss-mysql-requirement-6/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>PCI DSS &amp; MySQL &#8211; Requirement 4</title>
		<link>http://www.pablowe.net/2010/04/pci-dss-mysql-requirement-4/</link>
		<comments>http://www.pablowe.net/2010/04/pci-dss-mysql-requirement-4/#comments</comments>
		<pubDate>Wed, 07 Apr 2010 19:14:45 +0000</pubDate>
		<dc:creator>rlowe</dc:creator>
				<category><![CDATA[MySQL]]></category>
		<category><![CDATA[MySQL Administration]]></category>
		<category><![CDATA[PCI DSS]]></category>
		<category><![CDATA[Security]]></category>
		<category><![CDATA[MySQL Security]]></category>

		<guid isPermaLink="false">http://www.pablowe.net/?p=513</guid>
		<description><![CDATA[Requirement 4 of PCI DSS v1.2 states that we must: &#8220;Encrypt transmission of cardholder data across open, public networks&#8221; Specifically, &#8220;Sensitive information must be encrypted during transmission over networks that are easily accessed by malicious individuals. Misconfigured wireless networks and vulnerabilities in legacy encryption and authentication protocols can be continued targets of malicious individuals who [...]]]></description>
		<wfw:commentRss>http://www.pablowe.net/2010/04/pci-dss-mysql-requirement-4/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>PCI DSS &amp; MySQL: Requirement 3</title>
		<link>http://www.pablowe.net/2010/04/pci-dss-mysql-requirement-3/</link>
		<comments>http://www.pablowe.net/2010/04/pci-dss-mysql-requirement-3/#comments</comments>
		<pubDate>Wed, 07 Apr 2010 14:27:51 +0000</pubDate>
		<dc:creator>rlowe</dc:creator>
				<category><![CDATA[MySQL]]></category>
		<category><![CDATA[PCI DSS]]></category>
		<category><![CDATA[Security]]></category>

		<guid isPermaLink="false">http://www.pablowe.net/?p=447</guid>
		<description><![CDATA[Requirement 3 of the PCI DSS v1.2 is: &#8220;Protect Stored Cardholder Data&#8221; As vague as that sounds, the PCI DSS enumerates exactly what that covers: Data Element Storage Permitted Protection Required PCI DSS Req 3.4 Primary Account Number Yes Yes Yes Cardholder Name* Yes Yes No Service Code* Yes Yes No Expiration Date* Yes Yes [...]]]></description>
		<wfw:commentRss>http://www.pablowe.net/2010/04/pci-dss-mysql-requirement-3/feed/</wfw:commentRss>
		<slash:comments>3</slash:comments>
		</item>
		<item>
		<title>PCI DSS &amp; MySQL &#8211; Requirement 2</title>
		<link>http://www.pablowe.net/2010/04/pci-dss-mysql-requirement-2/</link>
		<comments>http://www.pablowe.net/2010/04/pci-dss-mysql-requirement-2/#comments</comments>
		<pubDate>Tue, 06 Apr 2010 14:54:58 +0000</pubDate>
		<dc:creator>rlowe</dc:creator>
				<category><![CDATA[MySQL]]></category>
		<category><![CDATA[PCI DSS]]></category>
		<category><![CDATA[Security]]></category>

		<guid isPermaLink="false">http://www.pablowe.net/?p=414</guid>
		<description><![CDATA[Requirement 2 of the PCI DSS v1.2 is: &#8220;Do not use vendor-supplied defaults for system passwords and other security parameters&#8221; Understanding that we&#8217;re limiting the discussion solely to MySQL (OS, Network Devices, and other software will no doubt apply to overall compliance), we can do this easily. The vendor-supplied default MySQL 5.1.43 (they&#8217;re similar across [...]]]></description>
		<wfw:commentRss>http://www.pablowe.net/2010/04/pci-dss-mysql-requirement-2/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>Nagios Checks For MMM</title>
		<link>http://www.pablowe.net/2009/07/nagios-checks-for-mmm/</link>
		<comments>http://www.pablowe.net/2009/07/nagios-checks-for-mmm/#comments</comments>
		<pubDate>Wed, 15 Jul 2009 22:06:41 +0000</pubDate>
		<dc:creator>rlowe</dc:creator>
				<category><![CDATA[MySQL]]></category>
		<category><![CDATA[MySQL Administration]]></category>
		<category><![CDATA[MMM]]></category>
		<category><![CDATA[Nagios]]></category>

		<guid isPermaLink="false">http://www.pablowe.net/?p=248</guid>
		<description><![CDATA[I&#8217;ve written some new Nagios checks for MMM (MMM on Google Code &#8230; MMM on Launchpad). check_mmm is a part of http://code.google.com/p/check-mysql-all/, and is meant to be called locally on the MMM Monitor server (usually via NRPE). Feedback is welcome, usage is as follows: Usage: check_mmm --cluster C# Options: --cluster= The MMM Cluster to check [...]]]></description>
		<wfw:commentRss>http://www.pablowe.net/2009/07/nagios-checks-for-mmm/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Nagios MySQL Plug-Ins</title>
		<link>http://www.pablowe.net/2009/03/nagios-mysql-plug-ins/</link>
		<comments>http://www.pablowe.net/2009/03/nagios-mysql-plug-ins/#comments</comments>
		<pubDate>Mon, 09 Mar 2009 06:22:25 +0000</pubDate>
		<dc:creator>rlowe</dc:creator>
				<category><![CDATA[MySQL]]></category>
		<category><![CDATA[MySQL Administration]]></category>
		<category><![CDATA[Nagios]]></category>

		<guid isPermaLink="false">http://www.pablowe.net/?p=198</guid>
		<description><![CDATA[There currently exist many plugins for MySQL to use with Nagios. Many of them, however, are not version-independent, leaving organizations that use multiple versions of MySQL to either install multiple plugins or not monitor specific versions of MySQL. As such, I&#8217;ve compiled what I consider to be the most useful checks into a single plugin: [...]]]></description>
		<wfw:commentRss>http://www.pablowe.net/2009/03/nagios-mysql-plug-ins/feed/</wfw:commentRss>
		<slash:comments>4</slash:comments>
		</item>
		<item>
		<title>The Awkward Stage of Scaling</title>
		<link>http://www.pablowe.net/2008/10/the-awkward-stage-of-scaling/</link>
		<comments>http://www.pablowe.net/2008/10/the-awkward-stage-of-scaling/#comments</comments>
		<pubDate>Fri, 10 Oct 2008 02:19:57 +0000</pubDate>
		<dc:creator>rlowe</dc:creator>
				<category><![CDATA[MySQL]]></category>
		<category><![CDATA[MySQL Performance]]></category>
		<category><![CDATA[Performance]]></category>
		<category><![CDATA[Data Sharding]]></category>
		<category><![CDATA[Functional Partitioning]]></category>

		<guid isPermaLink="false">http://www.pablowe.net/?p=134</guid>
		<description><![CDATA[A lot of my clients are in a position where their database performance is deteriorating but they are not &#8220;big enough&#8221; (or not willing/able to) explore sharding all of their data structures. They&#8217;re too big for the solution to be adding another read slave, but too small to justify the resources for re-designing their architecture. [...]]]></description>
		<wfw:commentRss>http://www.pablowe.net/2008/10/the-awkward-stage-of-scaling/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Managing MySQL Configuration Files</title>
		<link>http://www.pablowe.net/2008/09/managing-mysql-configuration-files/</link>
		<comments>http://www.pablowe.net/2008/09/managing-mysql-configuration-files/#comments</comments>
		<pubDate>Wed, 03 Sep 2008 21:08:40 +0000</pubDate>
		<dc:creator>rlowe</dc:creator>
				<category><![CDATA[MySQL]]></category>
		<category><![CDATA[MySQL Administration]]></category>
		<category><![CDATA[MySQL Configuration Management]]></category>

		<guid isPermaLink="false">http://www.pablowe.net/?p=80</guid>
		<description><![CDATA[It is good practice to manage changes to MySQL configuration files (/etc/my.cnf) by using a version control system. I usually use a home-brewed (not brewed by me!) svn+cfengine application to propagate my.cnf (and other configuration file) changes to defined classes of machines (classes are based on application role, replication role, etc). When managing hundreds of [...]]]></description>
		<wfw:commentRss>http://www.pablowe.net/2008/09/managing-mysql-configuration-files/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>MySQL&#8217;s PAGER</title>
		<link>http://www.pablowe.net/2008/06/mysqls-pager/</link>
		<comments>http://www.pablowe.net/2008/06/mysqls-pager/#comments</comments>
		<pubDate>Wed, 25 Jun 2008 04:43:01 +0000</pubDate>
		<dc:creator>rlowe</dc:creator>
				<category><![CDATA[MySQL]]></category>
		<category><![CDATA[Perl]]></category>

		<guid isPermaLink="false">http://www.pablowe.net/?p=21</guid>
		<description><![CDATA[Baron Schwartz wrote a neat article on MySQL&#8217;s pager command yesterday. As a followup, I thought I would post what I use as my default PAGER environmental variable. It simply substitutes mk-visual-explain for MySQL&#8217;s EXPLAIN command and uses less if the output is taller than your current terminal window (note, this currently renders \G non-functional): [...]]]></description>
		<wfw:commentRss>http://www.pablowe.net/2008/06/mysqls-pager/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Using Nagios as a MySQL Performance Profiler</title>
		<link>http://www.pablowe.net/2008/06/using-nagios-as-a-mysql-performance-profiler/</link>
		<comments>http://www.pablowe.net/2008/06/using-nagios-as-a-mysql-performance-profiler/#comments</comments>
		<pubDate>Tue, 17 Jun 2008 23:37:16 +0000</pubDate>
		<dc:creator>rlowe</dc:creator>
				<category><![CDATA[MySQL]]></category>
		<category><![CDATA[MySQL Performance]]></category>
		<category><![CDATA[Nagios]]></category>

		<guid isPermaLink="false">http://www.pablowe.net/?p=6</guid>
		<description><![CDATA[Everybody knows than Nagios can be used as a service monitor to monitor things like Load Averages, MySQL Replication Status, RAID Array States, etc&#8230; Fewer know that there are plug-ins to monitor MySQL Performance Status, such as check_mysql_perf. Fewer still utilize Nagios&#8217; built-in triggering mechanism to execute an additional script on the event of a [...]]]></description>
		<wfw:commentRss>http://www.pablowe.net/2008/06/using-nagios-as-a-mysql-performance-profiler/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
	</channel>
</rss>
