<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>QEP on Enterprise Data Architect | Principal Data Strategist |  MySQL Subject Matter Expert |  Author | Speaker</title>
    <link>https://ronaldbradford.com/tags/qep/</link>
    <description>Recent content in QEP on Enterprise Data Architect | Principal Data Strategist |  MySQL Subject Matter Expert |  Author | Speaker</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-us</language>
    <lastBuildDate>Mon, 13 Jun 2011 16:53:03 +0000</lastBuildDate>
    <atom:link href="https://ronaldbradford.com/tags/qep/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Utilizing multiple indexes per MySQL table join</title>
      <link>https://ronaldbradford.com/blog/utilizing-multiple-index-per-mysql-table-join-2011-06-13/</link>
      <pubDate>Mon, 13 Jun 2011 16:53:03 +0000</pubDate>
      <guid>https://ronaldbradford.com/blog/utilizing-multiple-index-per-mysql-table-join-2011-06-13/</guid>
      <description>Historically it was considered that MySQL will generally use only one index per referenced table in a SQL query. In MySQL 5.0 the introduction of merge indexes enabled for certain conditions the possibility to utilize two indexes however this could result in worst performance then creating a better index.</description>
    </item>
    <item>
      <title>Extra: Using Index</title>
      <link>https://ronaldbradford.com/blog/extra-using-index-2011-06-13/</link>
      <pubDate>Mon, 13 Jun 2011 16:48:26 +0000</pubDate>
      <guid>https://ronaldbradford.com/blog/extra-using-index-2011-06-13/</guid>
      <description>Many people consider this information in the MySQL Query Execution Plan (QEP) to indicate that the referenced table is using an index. It actually means that ONLY the index is used.</description>
    </item>
    <item>
      <title>Optimizing UPDATE and DELETE statements</title>
      <link>https://ronaldbradford.com/blog/optimizing-update-and-delete-statements-2011-02-24/</link>
      <pubDate>Thu, 24 Feb 2011 04:01:01 +0000</pubDate>
      <guid>https://ronaldbradford.com/blog/optimizing-update-and-delete-statements-2011-02-24/</guid>
      <description>Updated Nov 2011. Check out my latest book on Optimizing SQL Statements for more information. MySQL 5.6.2 also now provides an EXPLAIN syntax for UPDATE and DELETE statements natively.&#xA;While most people look at performance optimizations for SELECT statements, UPDATE and DELETE statements are often overlooked.</description>
    </item>
    <item>
      <title>EXPLAIN –  An essential tool for MySQL developers.</title>
      <link>https://ronaldbradford.com/blog/explain-an-essential-tool-for-mysql-developers-2009-09-26/</link>
      <pubDate>Sat, 26 Sep 2009 15:46:45 +0000</pubDate>
      <guid>https://ronaldbradford.com/blog/explain-an-essential-tool-for-mysql-developers-2009-09-26/</guid>
      <description>Just recently I came across the presentation “Bend SQL to your will with EXPLAIN” by Ligaya Turmelle via the Linked In – MySQL Speakers and Presenters group. Slides available at Slideshare .</description>
    </item>
    <item>
      <title>We need more CATs</title>
      <link>https://ronaldbradford.com/blog/we-need-more-cats-2009-08-22/</link>
      <pubDate>Sat, 22 Aug 2009 05:44:11 +0000</pubDate>
      <guid>https://ronaldbradford.com/blog/we-need-more-cats-2009-08-22/</guid>
      <description>Before you think I’ve posted an animal story in my MySQL category please read on. For reference, The RAT and the CAT is something I wrote back in 2006, that explains the CAT part.</description>
    </item>
    <item>
      <title>Understanding Different MySQL Index Implementations</title>
      <link>https://ronaldbradford.com/blog/understanding-different-mysql-index-implementations-2009-07-22/</link>
      <pubDate>Thu, 23 Jul 2009 00:37:20 +0000</pubDate>
      <guid>https://ronaldbradford.com/blog/understanding-different-mysql-index-implementations-2009-07-22/</guid>
      <description>It is important to know and understand that while indexing columns in MySQL will generally improve performance, using the appropriate type of index can make a greater impact on performance.</description>
    </item>
    <item>
      <title>A 5.1 QEP nicety – Using join buffer</title>
      <link>https://ronaldbradford.com/blog/a-51-qep-nicety-using-join-buffer-2008-08-27/</link>
      <pubDate>Wed, 27 Aug 2008 15:56:23 +0000</pubDate>
      <guid>https://ronaldbradford.com/blog/a-51-qep-nicety-using-join-buffer-2008-08-27/</guid>
      <description>I was surprised to find yesterday when using MySQL 5.1.26-rc with a client I’m recommending 5.1 to, some information not seen in the EXPLAIN plan before while reviewing SQL Statements.</description>
    </item>
  </channel>
</rss>
