<?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: select jsto jest optimisation in Application Development and Automation Discussions</title>
    <link>https://community.sap.com/t5/application-development-and-automation-discussions/select-jsto-jest-optimisation/m-p/838618#M44005</link>
    <description>&lt;P&gt;I really don't know JSTO, not JEST, but it looks like you can use some kind of JOIN instead of using EXISTS.&lt;/P&gt;&lt;P&gt;J.&lt;/P&gt;</description>
    <pubDate>Wed, 23 Jan 2019 20:57:49 GMT</pubDate>
    <dc:creator>Jean_Sagi</dc:creator>
    <dc:date>2019-01-23T20:57:49Z</dc:date>
    <item>
      <title>select jsto jest optimisation</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/select-jsto-jest-optimisation/m-p/838615#M44002</link>
      <description>&lt;P&gt;Hello Folks, &lt;/P&gt;
  &lt;P&gt;i'm trying to optimize a select really poor on performance, any idea on how to change the join in order to have a better performance please?&lt;/P&gt;
  &lt;PRE&gt;&lt;CODE&gt; SELECT objnr FROM jsto AS a APPENDING CORRESPONDING FIELDS OF

                      TABLE onr_tab WHERE a~objnr IN r_s_objnr AND

                                          a~obtyp EQ sdcon-item AND

                                          a~stsma NE stsma_ini AND

             EXISTS ( SELECT objnr FROM jest WHERE objnr EQ a~objnr AND

                     stat LIKE 'E%' AND inact EQ space ) ORDER BY OBJNR.&lt;/CODE&gt;&lt;/PRE&gt;</description>
      <pubDate>Wed, 23 Jan 2019 13:31:33 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/select-jsto-jest-optimisation/m-p/838615#M44002</guid>
      <dc:creator>marco_sposa</dc:creator>
      <dc:date>2019-01-23T13:31:33Z</dc:date>
    </item>
    <item>
      <title>Re: select jsto jest optimisation</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/select-jsto-jest-optimisation/m-p/838616#M44003</link>
      <description>&lt;P&gt;Are views V_STAT or V_JSTO_JEST active in your database, else did you check access plan from a &lt;A href="https://help.sap.com/viewer/search?q=access%20path%20sql%20trace"&gt;SQL trace&lt;/A&gt;?&lt;/P&gt;</description>
      <pubDate>Wed, 23 Jan 2019 14:32:59 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/select-jsto-jest-optimisation/m-p/838616#M44003</guid>
      <dc:creator>RaymondGiuseppi</dc:creator>
      <dc:date>2019-01-23T14:32:59Z</dc:date>
    </item>
    <item>
      <title>Re: select jsto jest optimisation</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/select-jsto-jest-optimisation/m-p/838617#M44004</link>
      <description>&lt;P&gt;yes they are both active in the database.&lt;/P&gt;&lt;P&gt;i will start using them and may changing the query by doing 2 selects then using two selects instead of one ( using for all entries ).&lt;/P&gt;&lt;P&gt;Am i in the good direction?&lt;/P&gt;</description>
      <pubDate>Wed, 23 Jan 2019 14:56:44 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/select-jsto-jest-optimisation/m-p/838617#M44004</guid>
      <dc:creator>marco_sposa</dc:creator>
      <dc:date>2019-01-23T14:56:44Z</dc:date>
    </item>
    <item>
      <title>Re: select jsto jest optimisation</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/select-jsto-jest-optimisation/m-p/838618#M44005</link>
      <description>&lt;P&gt;I really don't know JSTO, not JEST, but it looks like you can use some kind of JOIN instead of using EXISTS.&lt;/P&gt;&lt;P&gt;J.&lt;/P&gt;</description>
      <pubDate>Wed, 23 Jan 2019 20:57:49 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/select-jsto-jest-optimisation/m-p/838618#M44005</guid>
      <dc:creator>Jean_Sagi</dc:creator>
      <dc:date>2019-01-23T20:57:49Z</dc:date>
    </item>
    <item>
      <title>Re: select jsto jest optimisation</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/select-jsto-jest-optimisation/m-p/838619#M44006</link>
      <description>&lt;P&gt;Please attach the Execution Plan to your question, otherwise how can you know where the issue is!? (aka access plan as said Raymond)&lt;/P&gt;</description>
      <pubDate>Wed, 23 Jan 2019 20:59:35 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/select-jsto-jest-optimisation/m-p/838619#M44006</guid>
      <dc:creator>Sandra_Rossi</dc:creator>
      <dc:date>2019-01-23T20:59:35Z</dc:date>
    </item>
    <item>
      <title>Re: select jsto jest optimisation</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/select-jsto-jest-optimisation/m-p/838620#M44007</link>
      <description>&lt;P&gt;thanx you all by using the view V_JSTO_JEST (and the program logic) i solved the issue, the performance is now acceptable &lt;/P&gt;</description>
      <pubDate>Sun, 27 Jan 2019 12:11:01 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/select-jsto-jest-optimisation/m-p/838620#M44007</guid>
      <dc:creator>marco_sposa</dc:creator>
      <dc:date>2019-01-27T12:11:01Z</dc:date>
    </item>
    <item>
      <title>Re: select jsto jest optimisation</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/select-jsto-jest-optimisation/m-p/838621#M44008</link>
      <description>&lt;P&gt;thx for the feedback ! please use the option to convert your "answer" into a comment, under Raymond's answer&lt;/P&gt;</description>
      <pubDate>Sun, 27 Jan 2019 12:58:59 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/select-jsto-jest-optimisation/m-p/838621#M44008</guid>
      <dc:creator>Sandra_Rossi</dc:creator>
      <dc:date>2019-01-27T12:58:59Z</dc:date>
    </item>
    <item>
      <title>Re: select jsto jest optimisation</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/select-jsto-jest-optimisation/m-p/838622#M44009</link>
      <description>&lt;P&gt;"then using two selects instead of one ( using for all entries ). Am i in the good direction?"&lt;/P&gt;&lt;P&gt;No. That's exactly the wrong thing to do. Don't do it.&lt;/P&gt;</description>
      <pubDate>Sun, 27 Jan 2019 16:28:06 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/select-jsto-jest-optimisation/m-p/838622#M44009</guid>
      <dc:creator>matt</dc:creator>
      <dc:date>2019-01-27T16:28:06Z</dc:date>
    </item>
  </channel>
</rss>

