<?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 create index in Application Development and Automation Discussions</title>
    <link>https://community.sap.com/t5/application-development-and-automation-discussions/create-index/m-p/1541040#M246492</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi all,&lt;/P&gt;&lt;P&gt;       how to create index for table GLPCA for fields RYEAR and POPER and how to write select statement using those indexes.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Mon, 21 Aug 2006 14:22:36 GMT</pubDate>
    <dc:creator>Former Member</dc:creator>
    <dc:date>2006-08-21T14:22:36Z</dc:date>
    <item>
      <title>create index</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/create-index/m-p/1541040#M246492</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi all,&lt;/P&gt;&lt;P&gt;       how to create index for table GLPCA for fields RYEAR and POPER and how to write select statement using those indexes.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 21 Aug 2006 14:22:36 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/create-index/m-p/1541040#M246492</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2006-08-21T14:22:36Z</dc:date>
    </item>
    <item>
      <title>Re: create index</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/create-index/m-p/1541041#M246493</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Use transaction SE11. There is a pushbutton 'INDEXES'. To use it, the SQL optimizer should use it itself. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;However, there is an abap command in which you can force the index to be used. Will try and find out. Can't remember it.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 21 Aug 2006 14:24:50 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/create-index/m-p/1541041#M246493</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2006-08-21T14:24:50Z</dc:date>
    </item>
    <item>
      <title>Re: create index</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/create-index/m-p/1541042#M246494</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Generally, and specifically with Oracle, if you include the fields of the index in the where clause of your SQL, the index will be chosen as part of the plan.  But the optimizer makes the final decision.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;After you create your index, ask your DBA to create statistics for it, so that the optimizer knows all about it.  Generally, you should let the optimizer decide the best course of action, and avoid "Hints"&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Look for function modules like "DB&lt;STRONG&gt;EXPLAIN&lt;/STRONG&gt;" that will give you an idea of what the optimizer will do.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;e.g.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;SELECT...&lt;/P&gt;&lt;P&gt;FROM GLPCA&lt;/P&gt;&lt;P&gt;WHERE RYEAR = l_var1&lt;/P&gt;&lt;P&gt;and POPER = l_VAR2&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 21 Aug 2006 14:31:37 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/create-index/m-p/1541042#M246494</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2006-08-21T14:31:37Z</dc:date>
    </item>
    <item>
      <title>Re: create index</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/create-index/m-p/1541043#M246495</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;If you know the controlling area (KOKRS), you can add that to the select statement. That should speed it up.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;It's not generally a good idea to add a custom index to a standard SAP table to speed up a single custom report.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Rob&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 21 Aug 2006 15:19:16 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/create-index/m-p/1541043#M246495</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2006-08-21T15:19:16Z</dc:date>
    </item>
  </channel>
</rss>

