<?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: SQl  excecute plan in Application Development and Automation Discussions</title>
    <link>https://community.sap.com/t5/application-development-and-automation-discussions/sql-excecute-plan/m-p/1092724#M101269</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi again,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Estimated Cost: 2&lt;/P&gt;&lt;P&gt;The estimated cost is a number assigned to the query and is&lt;/P&gt;&lt;P&gt;primarily used as a comparison to other query paths.  When this&lt;/P&gt;&lt;P&gt;query is run over and over again this number may vary slightly. &lt;/P&gt;&lt;P&gt;This number is useful when a change is made to the query (i.e.&lt;/P&gt;&lt;P&gt;adding an index) and it drops significantly. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Estimated # of Rows Returned: 8&lt;/P&gt;&lt;P&gt;The estimated number of rows returned is only an estimate.  There are queries which returns thousands of rows and this number&lt;/P&gt;&lt;P&gt;is only 2 or 3.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;regards,&lt;/P&gt;&lt;P&gt;amit m.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Tue, 27 Dec 2005 11:39:49 GMT</pubDate>
    <dc:creator>Former Member</dc:creator>
    <dc:date>2005-12-27T11:39:49Z</dc:date>
    <item>
      <title>SQl  excecute plan</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/sql-excecute-plan/m-p/1092721#M101266</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;SQL Statement&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;SELECT&lt;/P&gt;&lt;P&gt;  "VBELN" , "PARVW" , "KUNNR"&lt;/P&gt;&lt;P&gt;FROM&lt;/P&gt;&lt;P&gt;  "VBPA"&lt;/P&gt;&lt;P&gt;WHERE&lt;/P&gt;&lt;P&gt;  "MANDT" = '210' AND "VBELN" IN ( '400000','400019','400019','400066','400066','500000' ) AND (&lt;/P&gt;&lt;P&gt;  "PARVW" = 'AG' OR "PARVW" = 'RE' )&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Execution Plan&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt; SELECT STATEMENT ( Estimated Costs = 1 , Estimated #Rows = 8 )&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;        3 INLIST ITERATOR&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;            2 TABLE ACCESS BY INDEX ROWID VBPA&lt;/P&gt;&lt;P&gt;              ( Estim. Costs = 1 , Estim. #Rows = 8 )&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;                1 INDEX RANGE SCAN VBPA~Z01&lt;/P&gt;&lt;P&gt;                  ( Estim. Costs = 2 , Estim. #Rows = 8 )&lt;/P&gt;&lt;P&gt;                  Search Columns: 3&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;lt;b&amp;gt;Could you give me a explanation of this excecute plan aboved ?&amp;lt;/b&amp;gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 27 Dec 2005 08:10:12 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/sql-excecute-plan/m-p/1092721#M101266</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2005-12-27T08:10:12Z</dc:date>
    </item>
    <item>
      <title>Re: SQl  excecute plan</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/sql-excecute-plan/m-p/1092722#M101267</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi guixin,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;1. SELECT STATEMENT ( Estimated Costs = 1 , Estimated #Rows = 8 )&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;  It says that the command given to the&lt;/P&gt;&lt;P&gt;   database is a select statement.&lt;/P&gt;&lt;P&gt;  (other commands like insert, delete are also possible)&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;2.INLIST ITERATOR&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;  The database has to do some additional&lt;/P&gt;&lt;P&gt;  process based upon the SQL.&lt;/P&gt;&lt;P&gt;  The sql contains an IN statement.&lt;/P&gt;&lt;P&gt;VBELN" IN ( '400000','400019','400019','400066','400066','500000' &lt;/P&gt;&lt;P&gt; &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;3. TABLE ACCESS BY INDEX ROWID VBPA&lt;/P&gt;&lt;P&gt;( Estim. Costs = 1 , Estim. #Rows = 8 )&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt; The database has accessed the table&lt;/P&gt;&lt;P&gt;and used an index available on the table&lt;/P&gt;&lt;P&gt;instead of FULL SCAN on the table.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;4. 1 INDEX RANGE SCAN VBPA~Z01&lt;/P&gt;&lt;P&gt;( Estim. Costs = 2 , Estim. #Rows = 8 )&lt;/P&gt;&lt;P&gt;Search Columns: 3&lt;/P&gt;&lt;P&gt; Based upon the index, the database&lt;/P&gt;&lt;P&gt;  scanned the table based upon rowid&lt;/P&gt;&lt;P&gt; and as required, searched for 3 columns.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;regards,&lt;/P&gt;&lt;P&gt;amit m.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 27 Dec 2005 08:31:07 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/sql-excecute-plan/m-p/1092722#M101267</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2005-12-27T08:31:07Z</dc:date>
    </item>
    <item>
      <title>Re: SQl  excecute plan</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/sql-excecute-plan/m-p/1092723#M101268</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;HI:&lt;/P&gt;&lt;P&gt;   Could you explain "Estim. Costs = 2 , Estim. #Rows = 8"&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 27 Dec 2005 11:21:26 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/sql-excecute-plan/m-p/1092723#M101268</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2005-12-27T11:21:26Z</dc:date>
    </item>
    <item>
      <title>Re: SQl  excecute plan</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/sql-excecute-plan/m-p/1092724#M101269</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi again,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Estimated Cost: 2&lt;/P&gt;&lt;P&gt;The estimated cost is a number assigned to the query and is&lt;/P&gt;&lt;P&gt;primarily used as a comparison to other query paths.  When this&lt;/P&gt;&lt;P&gt;query is run over and over again this number may vary slightly. &lt;/P&gt;&lt;P&gt;This number is useful when a change is made to the query (i.e.&lt;/P&gt;&lt;P&gt;adding an index) and it drops significantly. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Estimated # of Rows Returned: 8&lt;/P&gt;&lt;P&gt;The estimated number of rows returned is only an estimate.  There are queries which returns thousands of rows and this number&lt;/P&gt;&lt;P&gt;is only 2 or 3.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;regards,&lt;/P&gt;&lt;P&gt;amit m.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 27 Dec 2005 11:39:49 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/sql-excecute-plan/m-p/1092724#M101269</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2005-12-27T11:39:49Z</dc:date>
    </item>
    <item>
      <title>Re: SQl  excecute plan</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/sql-excecute-plan/m-p/1092725#M101270</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;pls reward points if u have find any answers helpful.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;regards,&lt;/P&gt;&lt;P&gt;amit m.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 27 Dec 2005 12:48:28 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/sql-excecute-plan/m-p/1092725#M101270</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2005-12-27T12:48:28Z</dc:date>
    </item>
  </channel>
</rss>

