<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Merge Indexes on Enterprise Data Architect | Principal Data Strategist |  MySQL Subject Matter Expert |  Author | Speaker</title>
    <link>https://ronaldbradford.com/tags/merge-indexes/</link>
    <description>Recent content in Merge Indexes 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/merge-indexes/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>
  </channel>
</rss>
