<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Concepts SQL in Application Development and Automation Discussions</title>
    <link>https://community.sap.com/t5/application-development-and-automation-discussions/concepts-sql/m-p/1840723#M357296</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Check this:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;/people/rob.burbank/blog/2006/09/13/using-an-index-when-you-dont-have-all-of-the-fields&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;What I'm saying there is that if you are missing say the first field of a key, it's worth you while to take some extra measures to get that field (at least in Oracle and DB2).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Rob&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Message was edited by: &lt;/P&gt;&lt;P&gt;        Rob Burbank&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 24 Jan 2007 19:38:21 GMT</pubDate>
    <dc:creator>Former Member</dc:creator>
    <dc:date>2007-01-24T19:38:21Z</dc:date>
    <item>
      <title>Concepts SQL</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/concepts-sql/m-p/1840721#M357294</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi everybody&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Can somebody help me with this two concepts:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If i have a Table with two key Fields:   &lt;/P&gt;&lt;P&gt; &lt;/P&gt;&lt;P&gt;FieldA     key&lt;/P&gt;&lt;P&gt;FieldB     Key&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;a) If i make a Select  using both key fields, but the first key field is not resctricted:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;SELECT... WHERE   &lt;/P&gt;&lt;P&gt;FieldA     IN      SelOptsA   AND   &amp;lt;-- empty range         &lt;/P&gt;&lt;P&gt;FieldB     IN      SelOptsB             &amp;lt;-- range with one value&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The select uses the Index even the first key is not filled ?  &lt;/P&gt;&lt;P&gt;Even if the select really is not resctricting any value for the first key field , but is taking all values for that FieldA.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;b)  If i make a Select using first another Field wich is not key, but it's not restricted:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;SELECT....WHERE    &lt;/P&gt;&lt;P&gt;FieldX     IN     SelOptsX    AND     &amp;lt;-- empty range&lt;/P&gt;&lt;P&gt;FieldA    IN     SelOptsA    AND     &amp;lt;-- range with one value&lt;/P&gt;&lt;P&gt;FieldB    IN     SelOptsB                &amp;lt;-- range with one value&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The select is 'inteligent' for use the Index ?&lt;/P&gt;&lt;P&gt;That is, the select can detect that first field (FieldX) has not really a restriction (it's taking all values) and see that the next fields restricted are in a Index ?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;(I do not know if a Select first check what fields are really restricted and what are restricted to ALL values; for get the fields restricted and search an Index wich compliance the key)&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;&lt;P&gt;Frank&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 24 Jan 2007 19:06:11 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/concepts-sql/m-p/1840721#M357294</guid>
      <dc:creator>former_member425121</dc:creator>
      <dc:date>2007-01-24T19:06:11Z</dc:date>
    </item>
    <item>
      <title>Re: Concepts SQL</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/concepts-sql/m-p/1840722#M357295</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Frank,  it appears that you may be questioning the optimizer's methods.  I will not comment on what I think the optimizer is doing, because I simply don't know and it may be different from system to system and database to database. So all I can offer is a little reading material.  I will say that the optimizer is looking for the best access path and it is looking at the avaiable indexes as well as the restrictions in your WHERE clause.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://help.sap.com/saphelp_nw04s/helpdata/en/fb/36fe3b34334a7be10000000a114084/frameset.htm" target="test_blank"&gt;http://help.sap.com/saphelp_nw04s/helpdata/en/fb/36fe3b34334a7be10000000a114084/frameset.htm&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://help.sap.com/saphelp_nw04s/helpdata/en/2d/0ef63ebdee3a4c958f51cfee32ad3a/frameset.htm" target="test_blank"&gt;http://help.sap.com/saphelp_nw04s/helpdata/en/2d/0ef63ebdee3a4c958f51cfee32ad3a/frameset.htm&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Rich Heilman&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 24 Jan 2007 19:24:20 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/concepts-sql/m-p/1840722#M357295</guid>
      <dc:creator>RichHeilman</dc:creator>
      <dc:date>2007-01-24T19:24:20Z</dc:date>
    </item>
    <item>
      <title>Re: Concepts SQL</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/concepts-sql/m-p/1840723#M357296</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Check this:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;/people/rob.burbank/blog/2006/09/13/using-an-index-when-you-dont-have-all-of-the-fields&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;What I'm saying there is that if you are missing say the first field of a key, it's worth you while to take some extra measures to get that field (at least in Oracle and DB2).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Rob&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Message was edited by: &lt;/P&gt;&lt;P&gt;        Rob Burbank&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 24 Jan 2007 19:38:21 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/concepts-sql/m-p/1840723#M357296</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-01-24T19:38:21Z</dc:date>
    </item>
    <item>
      <title>Re: Concepts SQL</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/concepts-sql/m-p/1840724#M357297</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I agree with Rob. If you do not have the first key field, your performance would be adversely impacted.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 24 Jan 2007 20:15:31 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/concepts-sql/m-p/1840724#M357297</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-01-24T20:15:31Z</dc:date>
    </item>
    <item>
      <title>Re: Concepts SQL</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/concepts-sql/m-p/1840725#M357298</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Thanks..&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 26 Jan 2007 17:12:49 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/concepts-sql/m-p/1840725#M357298</guid>
      <dc:creator>former_member425121</dc:creator>
      <dc:date>2007-01-26T17:12:49Z</dc:date>
    </item>
  </channel>
</rss>

