<?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: Index in Application Development and Automation Discussions</title>
    <link>https://community.sap.com/t5/application-development-and-automation-discussions/index/m-p/1614006#M275128</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The where condition in the select statement should have all the fields defined in the index in the same sequence.Ofcourse queries which hit index are faster than the queries which do not hit the index. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You can force the database to pick the index by using database Hints.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Hope this helps.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Fri, 06 Oct 2006 06:12:14 GMT</pubDate>
    <dc:creator>Former Member</dc:creator>
    <dc:date>2006-10-06T06:12:14Z</dc:date>
    <item>
      <title>Index</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/index/m-p/1614005#M275127</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;      I have a small doubt.&lt;/P&gt;&lt;P&gt;A select statement is queried on 5 fields&lt;/P&gt;&lt;P&gt;Eg : &lt;/P&gt;&lt;P&gt;select a b c&lt;/P&gt;&lt;P&gt;from table1&lt;/P&gt;&lt;P&gt;where field1 eq p&lt;/P&gt;&lt;P&gt;      field2 eq q      &lt;/P&gt;&lt;P&gt;      field3 eq r&lt;/P&gt;&lt;P&gt;      field4 eq s&lt;/P&gt;&lt;P&gt;      field5 eq t.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Suppose there is an index created for the table on field2 and field3.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Already the query is running with index on field2 and field3. If I create another index with all the fields in the where clause, will there be considerable perfomance improvement?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks in advance.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Vishnu Priya&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Message was edited by: Vishnu priya&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 06 Oct 2006 06:09:47 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/index/m-p/1614005#M275127</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2006-10-06T06:09:47Z</dc:date>
    </item>
    <item>
      <title>Re: Index</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/index/m-p/1614006#M275128</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The where condition in the select statement should have all the fields defined in the index in the same sequence.Ofcourse queries which hit index are faster than the queries which do not hit the index. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You can force the database to pick the index by using database Hints.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Hope this helps.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 06 Oct 2006 06:12:14 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/index/m-p/1614006#M275128</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2006-10-06T06:12:14Z</dc:date>
    </item>
    <item>
      <title>Re: Index</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/index/m-p/1614007#M275129</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;just refer amit answer  ur  point  will clear...&lt;/P&gt;&lt;P&gt;&lt;A class="jive_macro jive_macro_message" href="https://community.sap.com/" __jive_macro_name="message" modifiedtitle="true" __default_attr="2449360"&gt;&lt;/A&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 06 Oct 2006 06:13:31 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/index/m-p/1614007#M275129</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2006-10-06T06:13:31Z</dc:date>
    </item>
    <item>
      <title>Re: Index</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/index/m-p/1614008#M275130</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;The primary index contains the key fields of the table and a pointer to the non-key fields of the table. The primary index is created automatically when the table is created in the database.&lt;/P&gt;&lt;P&gt;If you have the Index with your Where clause fields, you can use that to improve your Select statmnet performence ..&lt;/P&gt;&lt;P&gt;You can force the sql statement to use a particular index by using %_HINTS parameter. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;For eg:&lt;/P&gt;&lt;P&gt;SELECT carrid connid cityfrom&lt;/P&gt;&lt;P&gt;FROM spfli INTO (xcarrid, xconnid, xcityfrom)&lt;/P&gt;&lt;P&gt;WHERE carrid = 'LH ' AND cityfrom = 'FRANKFURT'&lt;/P&gt;&lt;P&gt;%_HINTS ORACLE 'INDEX("SPFLI" "SPFLI~001")'.&lt;/P&gt;&lt;P&gt;WRITE: / xcarrid, xconnid, xcityfrom.&lt;/P&gt;&lt;P&gt;ENDSELECT.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Refer to the SAP Note #129385 and related notes for further information&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;P&gt;Sudheer&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 06 Oct 2006 06:32:54 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/index/m-p/1614008#M275130</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2006-10-06T06:32:54Z</dc:date>
    </item>
  </channel>
</rss>

