<?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: Performance issue in Application Development and Automation Discussions</title>
    <link>https://community.sap.com/t5/application-development-and-automation-discussions/performance-issue/m-p/1048852#M88670</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;K P - I think the 'WHERE essid IS not NULL' is doing you in. It will have to read all records in the database.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Since you don't want to create a secondary index, you could try reading the entire table into an internal table and then deleting the entries you don't want. This &amp;lt;i&amp;gt;might&amp;lt;/i&amp;gt; be faster but will use more memory.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Rob&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 23 Nov 2005 14:27:24 GMT</pubDate>
    <dc:creator>Former Member</dc:creator>
    <dc:date>2005-11-23T14:27:24Z</dc:date>
    <item>
      <title>Performance issue</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/performance-issue/m-p/1048849#M88667</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;&lt;/P&gt;&lt;P&gt;I have a Custom table for USERDETAILS, on which I am fetching data using &lt;/P&gt;&lt;P&gt;SELECT ecno bname  department l1name l2name bukrs&lt;/P&gt;&lt;P&gt;                     FROM yusrdetail&lt;/P&gt;&lt;P&gt;                     INTO TABLE vt_yusrdetail1&lt;/P&gt;&lt;P&gt;                     WHERE essid IS not NULL&lt;/P&gt;&lt;P&gt;                     AND department IN s_dept&lt;/P&gt;&lt;P&gt;                     AND bukrs IN s_bukrs.     &lt;/P&gt;&lt;P&gt;Here how can I improve performance of this Query with out creating index on DEPT and BUKRS.&lt;/P&gt;&lt;P&gt;INDEX is already existing on ESSID.&lt;/P&gt;&lt;P&gt;Here BNAME is the only Primary Key available on this table.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;It is very urgent Plz....&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanx &lt;/P&gt;&lt;P&gt;K P&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 23 Nov 2005 10:39:09 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/performance-issue/m-p/1048849#M88667</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2005-11-23T10:39:09Z</dc:date>
    </item>
    <item>
      <title>Re: Performance issue</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/performance-issue/m-p/1048850#M88668</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi K P,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Your select looks good, maybe, if you have a good idea of the number of result, you can be faster when you define your internal table. You just have to create the good size, that will be faster because SAP will not have to make dynamic allocation memory. &lt;/P&gt;&lt;P&gt;But, this solution is dangerous, cause you must know the number of lines you will have ...&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;data : vt_yusrdetail1 type table ....  initial size ...&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Rgd&lt;/P&gt;&lt;P&gt;Frédéric&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 23 Nov 2005 10:51:33 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/performance-issue/m-p/1048850#M88668</guid>
      <dc:creator>FredericGirod</dc:creator>
      <dc:date>2005-11-23T10:51:33Z</dc:date>
    </item>
    <item>
      <title>Re: Performance issue</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/performance-issue/m-p/1048851#M88669</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi try this &lt;/P&gt;&lt;P&gt;SELECT &amp;lt;b&amp;gt;bname  ecno&amp;lt;/b&amp;gt; department l1name l2name bukrs&lt;/P&gt;&lt;P&gt;FROM yusrdetail&lt;/P&gt;&lt;P&gt;INTO TABLE vt_yusrdetail1&lt;/P&gt;&lt;P&gt;WHERE essid IS not NULL&lt;/P&gt;&lt;P&gt;AND department IN s_dept&lt;/P&gt;&lt;P&gt;AND bukrs IN s_bukrs. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Hope this will help.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;regards&lt;/P&gt;&lt;P&gt;vijay&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 23 Nov 2005 10:51:38 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/performance-issue/m-p/1048851#M88669</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2005-11-23T10:51:38Z</dc:date>
    </item>
    <item>
      <title>Re: Performance issue</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/performance-issue/m-p/1048852#M88670</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;K P - I think the 'WHERE essid IS not NULL' is doing you in. It will have to read all records in the database.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Since you don't want to create a secondary index, you could try reading the entire table into an internal table and then deleting the entries you don't want. This &amp;lt;i&amp;gt;might&amp;lt;/i&amp;gt; be faster but will use more memory.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Rob&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 23 Nov 2005 14:27:24 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/performance-issue/m-p/1048852#M88670</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2005-11-23T14:27:24Z</dc:date>
    </item>
    <item>
      <title>Re: Performance issue</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/performance-issue/m-p/1048853#M88671</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;If essid is a numeric field and is a running number try providing a between clause instead of IS not NULL.&lt;/P&gt;&lt;P&gt;for e.g. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;SELECT ecno &lt;/P&gt;&lt;P&gt;       bname &lt;/P&gt;&lt;P&gt;       department &lt;/P&gt;&lt;P&gt;       l1name &lt;/P&gt;&lt;P&gt;       l2name &lt;/P&gt;&lt;P&gt;       bukrs&lt;/P&gt;&lt;P&gt;FROM yusrdetail&lt;/P&gt;&lt;P&gt;INTO TABLE vt_yusrdetail1&lt;/P&gt;&lt;P&gt;WHERE essid      between 1 and 9999999999&lt;/P&gt;&lt;P&gt;AND   department IN s_dept&lt;/P&gt;&lt;P&gt;AND   bukrs      IN s_bukrs.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;NOT in the where clause always by-passes index.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Kalpana&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 23 Nov 2005 14:56:44 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/performance-issue/m-p/1048853#M88671</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2005-11-23T14:56:44Z</dc:date>
    </item>
    <item>
      <title>Re: Performance issue</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/performance-issue/m-p/1048854#M88672</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Declare a range for ESSID and do not fill that range. You have to add the ESSID field to the internal table. IS NOT NULL is not a good option to use, because most table fields will be initialized to a non-null value. Change your select as follows and this way you will make it use the index on ESSID.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;PRE&gt;&lt;CODE&gt;
SELECT essid ecno bname department l1name l2name bukrs
  FROM yusrdetail
  INTO TABLE vt_yusrdetail1
 WHERE essid IN r_essid.

DELETE vt_yusrdetail1 WHERE essid is initial
                    AND NOT ( department IN s_dept AND 
                              bukrs      IN s_bukrs ). 
&lt;/CODE&gt;&lt;/PRE&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 23 Nov 2005 15:09:21 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/performance-issue/m-p/1048854#M88672</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2005-11-23T15:09:21Z</dc:date>
    </item>
  </channel>
</rss>

