<?xml version="1.0" encoding="UTF-8"?>
<!-- generator="FeedCreator 1.8" -->
<?xml-stylesheet href="https://www.omnidex.com/docs/v54/lib/exe/css.php?s=feed" type="text/css"?>
<rdf:RDF
    xmlns="http://purl.org/rss/1.0/"
    xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
    xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
    xmlns:dc="http://purl.org/dc/elements/1.1/">
    <channel rdf:about="https://www.omnidex.com/docs/v54/feed.php">
        <title>Documentation admin:optimization:plans</title>
        <description></description>
        <link>https://www.omnidex.com/docs/v54/</link>
        <image rdf:resource="https://www.omnidex.com/docs/v54/lib/tpl/simple/images/favicon.ico" />
       <dc:date>2026-04-29T17:59:00+0000</dc:date>
        <items>
            <rdf:Seq>
                <rdf:li rdf:resource="https://www.omnidex.com/docs/v54/doku.php?id=admin:optimization:plans:configuration&amp;rev=1467153531&amp;do=diff"/>
                <rdf:li rdf:resource="https://www.omnidex.com/docs/v54/doku.php?id=admin:optimization:plans:example&amp;rev=1467153531&amp;do=diff"/>
                <rdf:li rdf:resource="https://www.omnidex.com/docs/v54/doku.php?id=admin:optimization:plans:home&amp;rev=1467153531&amp;do=diff"/>
                <rdf:li rdf:resource="https://www.omnidex.com/docs/v54/doku.php?id=admin:optimization:plans:optimization&amp;rev=1467153531&amp;do=diff"/>
                <rdf:li rdf:resource="https://www.omnidex.com/docs/v54/doku.php?id=admin:optimization:plans:reference&amp;rev=1467153531&amp;do=diff"/>
            </rdf:Seq>
        </items>
    </channel>
    <image rdf:about="https://www.omnidex.com/docs/v54/lib/tpl/simple/images/favicon.ico">
        <title>Documentation</title>
        <link>https://www.omnidex.com/docs/v54/</link>
        <url>https://www.omnidex.com/docs/v54/lib/tpl/simple/images/favicon.ico</url>
    </image>
    <item rdf:about="https://www.omnidex.com/docs/v54/doku.php?id=admin:optimization:plans:configuration&amp;rev=1467153531&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2016-06-28T22:38:51+0000</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>admin:optimization:plans:configuration</title>
        <link>https://www.omnidex.com/docs/v54/doku.php?id=admin:optimization:plans:configuration&amp;rev=1467153531&amp;do=diff</link>
        <description>Administration: Optimizing Queries

Query Plans

Overview |
Anatomy of a Query Plan |
Reading a Query Plan |
Configuring Query Plans |
Optimizing Queries

----------




Configuring Query Plans

Omnidex Query Plans have some configuration options that will increase the amount of information available.  These are available using the SET EXPLAIN command in OdxSQL.  The syntax of the SET EXPLAIN command is:</description>
    </item>
    <item rdf:about="https://www.omnidex.com/docs/v54/doku.php?id=admin:optimization:plans:example&amp;rev=1467153531&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2016-06-28T22:38:51+0000</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>admin:optimization:plans:example</title>
        <link>https://www.omnidex.com/docs/v54/doku.php?id=admin:optimization:plans:example&amp;rev=1467153531&amp;do=diff</link>
        <description>Administration: Optimizing Queries

Query Plans

Overview |
Anatomy of a Query Plan |
Reading a Query Plan |
Configuring Query Plans |
Optimizing Queries

----------




Reading a Query Plan

The following is a rather straightforward query that joins two tables together --- Individuals and their respective Households --- and aggregates counts of all people born since 1980 that are either in Denver, CO or in Phoenix, AZ.  The result is a display of counts by Gender.  Let's take a look at the quer…</description>
    </item>
    <item rdf:about="https://www.omnidex.com/docs/v54/doku.php?id=admin:optimization:plans:home&amp;rev=1467153531&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2016-06-28T22:38:51+0000</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>admin:optimization:plans:home</title>
        <link>https://www.omnidex.com/docs/v54/doku.php?id=admin:optimization:plans:home&amp;rev=1467153531&amp;do=diff</link>
        <description>Administration: Optimizing Queries

Query Plans

Overview |
Anatomy of a Query Plan |
Reading a Query Plan |
Configuring Query Plans |
Optimizing Queries

----------

Overview

Omnidex always optimizes a query as well as it can using the Omnidex indexes; however, if the indexes are not enough, Omnidex will complete the query without indexes, insuring the correct result.  In fact, Omnidex can process queries even when no Omnidex indexes are available.  In this way, Omnidex is first and foremost a…</description>
    </item>
    <item rdf:about="https://www.omnidex.com/docs/v54/doku.php?id=admin:optimization:plans:optimization&amp;rev=1467153531&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2016-06-28T22:38:51+0000</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>admin:optimization:plans:optimization</title>
        <link>https://www.omnidex.com/docs/v54/doku.php?id=admin:optimization:plans:optimization&amp;rev=1467153531&amp;do=diff</link>
        <description>Administration: Optimizing Queries

Query Plans

Overview |
Anatomy of a Query Plan |
Reading a Query Plan |
Configuring Query Plans |
Optimizing Queries

----------




Optimizing Queries

The basic optimization of a query with Omnidex has six main steps. Most of the time, following these steps is enough to insure that the query performs well.</description>
    </item>
    <item rdf:about="https://www.omnidex.com/docs/v54/doku.php?id=admin:optimization:plans:reference&amp;rev=1467153531&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2016-06-28T22:38:51+0000</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>admin:optimization:plans:reference</title>
        <link>https://www.omnidex.com/docs/v54/doku.php?id=admin:optimization:plans:reference&amp;rev=1467153531&amp;do=diff</link>
        <description>Administration: Optimizing Queries

Query Plans

Overview |
Anatomy of a Query Plan |
Reading a Query Plan |
Configuring Query Plans |
Optimizing Queries

----------




Anatomy of a Query Plan

An Omnidex query plan is designed to provide all of the essential information needed to understand how a query will be processed, as well as basic suggestions about how to further optimize the query.  A great deal can be learned by reviewing the query plan, and it is always the first step in understandin…</description>
    </item>
</rdf:RDF>
