<?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: something better than join table in Application Development and Automation Discussions</title>
    <link>https://community.sap.com/t5/application-development-and-automation-discussions/something-better-than-join-table/m-p/687131#M30796</link>
    <description>&lt;P&gt;When you say "millions of records" do you mean in the tables or in the results? If the SELECT statement is fetching millions of rows, it will certainly take a lot of time no matter which method you use.&lt;/P&gt;
  &lt;P&gt;&lt;/P&gt;
  &lt;P&gt;A join itself cannot be bad for performance regardless of how many rows exist in joined tables, provided the join conditions are used correctly and the WHERE clause is using the correct indexes.&lt;/P&gt;
  &lt;P&gt;If it is not against your company policies, post the entire SELECT statement here and someone can offer some help.&lt;/P&gt;</description>
    <pubDate>Wed, 22 Aug 2018 17:00:34 GMT</pubDate>
    <dc:creator>P14397410</dc:creator>
    <dc:date>2018-08-22T17:00:34Z</dc:date>
    <item>
      <title>something better than join table</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/something-better-than-join-table/m-p/687130#M30795</link>
      <description>&lt;P&gt;Hallo Abapers,&lt;/P&gt;
  &lt;P&gt; &lt;/P&gt;
  &lt;P&gt;I have a programme to call the data from three tables and make segregation in some fields.&lt;BR /&gt;this has been developed&lt;STRONG&gt; on the join statement basis.&lt;/STRONG&gt;&lt;BR /&gt;&lt;BR /&gt;This program is taking sooooo much time now until we can see the result&lt;STRONG&gt; &lt;/STRONG&gt; tabel &lt;STRONG&gt;(if we can). &lt;/STRONG&gt;as we are talking here about millions of records !!!!&lt;BR /&gt;&lt;BR /&gt;Do you have some Ideas or other methods that are better and effecter than join tables to achieve this???&lt;/P&gt;
  &lt;P&gt; &lt;/P&gt;
  &lt;P&gt;Best Regards&lt;/P&gt;
  &lt;P&gt; &lt;/P&gt;
  &lt;P&gt;Jenie&lt;/P&gt;
  &lt;P&gt; &lt;/P&gt;</description>
      <pubDate>Wed, 22 Aug 2018 15:44:29 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/something-better-than-join-table/m-p/687130#M30795</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2018-08-22T15:44:29Z</dc:date>
    </item>
    <item>
      <title>Re: something better than join table</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/something-better-than-join-table/m-p/687131#M30796</link>
      <description>&lt;P&gt;When you say "millions of records" do you mean in the tables or in the results? If the SELECT statement is fetching millions of rows, it will certainly take a lot of time no matter which method you use.&lt;/P&gt;
  &lt;P&gt;&lt;/P&gt;
  &lt;P&gt;A join itself cannot be bad for performance regardless of how many rows exist in joined tables, provided the join conditions are used correctly and the WHERE clause is using the correct indexes.&lt;/P&gt;
  &lt;P&gt;If it is not against your company policies, post the entire SELECT statement here and someone can offer some help.&lt;/P&gt;</description>
      <pubDate>Wed, 22 Aug 2018 17:00:34 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/something-better-than-join-table/m-p/687131#M30796</guid>
      <dc:creator>P14397410</dc:creator>
      <dc:date>2018-08-22T17:00:34Z</dc:date>
    </item>
    <item>
      <title>Re: something better than join table</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/something-better-than-join-table/m-p/687132#M30797</link>
      <description>&lt;P&gt;Hi Jennifer,&lt;/P&gt;
  &lt;P&gt; &lt;/P&gt;
  &lt;P&gt; &lt;/P&gt;
  &lt;P&gt; &lt;/P&gt;
  &lt;P&gt;First of all, I suggest you consider analyzing that program issue before changing it.&lt;/P&gt;
  &lt;P&gt; &lt;/P&gt;
  &lt;P&gt; &lt;/P&gt;
  &lt;P&gt; &lt;/P&gt;
  &lt;P&gt;Following some steps to analyses program performance.&lt;/P&gt;
  &lt;P&gt; &lt;/P&gt;
  &lt;P&gt; &lt;/P&gt;
  &lt;P&gt; &lt;/P&gt;
  &lt;P&gt;1. SE30 or SAT (Runtime Analysis) transaction&lt;/P&gt;
  &lt;P&gt; &lt;/P&gt;
  &lt;P&gt; &lt;/P&gt;
  &lt;P&gt; &lt;/P&gt;
  &lt;P&gt;2. ST05 - SQL Trace (Performance Trace) transaction&lt;/P&gt;
  &lt;P&gt;Attached excellent documentation about SQL Trace&lt;BR /&gt;&lt;/P&gt;
  &lt;P&gt;&lt;/P&gt;
  &lt;P&gt;&lt;A href="https://wiki.scn.sap.com/wiki/display/SAPSQL/How+to+run+transaction+st05+to+trace+a+program%2C+transaction+or+user+execution" target="test_blank"&gt;https://wiki.scn.sap.com/wiki/display/SAPSQL/How+to+run+transaction+st05+to+trace+a+program%2C+transaction+or+user+execution&lt;/A&gt;&lt;/P&gt;
  &lt;P&gt;&lt;/P&gt;
  &lt;P&gt; &lt;/P&gt;
  &lt;P&gt; &lt;/P&gt;
  &lt;P&gt; &lt;/P&gt;
  &lt;P&gt;Depends on which tables it has retrieved data is dangerous creating/activating database view. &lt;/P&gt;
  &lt;P&gt; &lt;/P&gt;
  &lt;P&gt; &lt;/P&gt;
  &lt;P&gt; &lt;/P&gt;
  &lt;P&gt;Let us know the results.&lt;/P&gt;
  &lt;P&gt; &lt;/P&gt;
  &lt;P&gt; &lt;/P&gt;
  &lt;P&gt; &lt;/P&gt;
  &lt;P&gt;Regards&lt;/P&gt;</description>
      <pubDate>Wed, 22 Aug 2018 17:27:54 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/something-better-than-join-table/m-p/687132#M30797</guid>
      <dc:creator>roberto_forti</dc:creator>
      <dc:date>2018-08-22T17:27:54Z</dc:date>
    </item>
    <item>
      <title>Re: something better than join table</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/something-better-than-join-table/m-p/687133#M30798</link>
      <description>&lt;P&gt;You mean a "view" (ie vision?) ?&lt;/P&gt;</description>
      <pubDate>Wed, 22 Aug 2018 17:48:43 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/something-better-than-join-table/m-p/687133#M30798</guid>
      <dc:creator>ChrisSolomon</dc:creator>
      <dc:date>2018-08-22T17:48:43Z</dc:date>
    </item>
    <item>
      <title>Re: something better than join table</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/something-better-than-join-table/m-p/687134#M30799</link>
      <description>&lt;P&gt;Jennifer,&lt;/P&gt;
  &lt;P&gt;If you post the code, you will be able to get more accurate replies.&lt;/P&gt;
  &lt;P&gt;You can explore, OPEN CURSOR/FETCH CURSOR/CLOSE CURSOR.&lt;/P&gt;
  &lt;P&gt;K.Kiran.&lt;/P&gt;</description>
      <pubDate>Thu, 23 Aug 2018 13:13:19 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/something-better-than-join-table/m-p/687134#M30799</guid>
      <dc:creator>kiran_k8</dc:creator>
      <dc:date>2018-08-23T13:13:19Z</dc:date>
    </item>
    <item>
      <title>Re: something better than join table</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/something-better-than-join-table/m-p/687135#M30800</link>
      <description>&lt;P&gt;Hi Jennifer,&lt;/P&gt;
  &lt;P&gt;&lt;/P&gt;
  &lt;P&gt;on which DB is your system running?&lt;/P&gt;
  &lt;P&gt;&lt;/P&gt;
  &lt;P&gt;Kind regards,&lt;BR /&gt;Martin&lt;/P&gt;</description>
      <pubDate>Thu, 23 Aug 2018 13:24:45 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/something-better-than-join-table/m-p/687135#M30800</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2018-08-23T13:24:45Z</dc:date>
    </item>
  </channel>
</rss>

