<?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: rsdb/max_blocking_factor in Application Development and Automation Discussions</title>
    <link>https://community.sap.com/t5/application-development-and-automation-discussions/rsdb-max-blocking-factor/m-p/4212473#M1006618</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Split factor for FOR ALL ENTRIES queries&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A class="jive_macro jive_macro_thread" href="https://community.sap.com/" __jive_macro_name="thread" modifiedtitle="true" __default_attr="631728"&gt;&lt;/A&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 16 Jul 2008 11:41:56 GMT</pubDate>
    <dc:creator>Former Member</dc:creator>
    <dc:date>2008-07-16T11:41:56Z</dc:date>
    <item>
      <title>rsdb/max_blocking_factor</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/rsdb-max-blocking-factor/m-p/4212472#M1006617</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;What is rsdb/max_blocking_factor?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 16 Jul 2008 11:37:39 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/rsdb-max-blocking-factor/m-p/4212472#M1006617</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2008-07-16T11:37:39Z</dc:date>
    </item>
    <item>
      <title>Re: rsdb/max_blocking_factor</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/rsdb-max-blocking-factor/m-p/4212473#M1006618</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Split factor for FOR ALL ENTRIES queries&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A class="jive_macro jive_macro_thread" href="https://community.sap.com/" __jive_macro_name="thread" modifiedtitle="true" __default_attr="631728"&gt;&lt;/A&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 16 Jul 2008 11:41:56 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/rsdb-max-blocking-factor/m-p/4212473#M1006618</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2008-07-16T11:41:56Z</dc:date>
    </item>
    <item>
      <title>Re: rsdb/max_blocking_factor</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/rsdb-max-blocking-factor/m-p/4212474#M1006619</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;"The for all entries creates a where clause, where all the entries in the driver table are combined with OR. If the number of entries in the driver table is larger than rsdb/max_blocking_factor, several similar SQL statements are executed to limit the length of the WHERE clause.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;For example: you have 100 conditions generated by FOR ALL ENTRIES statement, the parameter is 5, then, the select statement is divided into 20 select sql with 5 conditions in where clause in each sql.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;It is related to the performance of FOR ALL ENTRIES.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;But not the larger the better. You can try, and it depends or your server machine.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 18 Jul 2008 10:42:18 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/rsdb-max-blocking-factor/m-p/4212474#M1006619</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2008-07-18T10:42:18Z</dc:date>
    </item>
  </channel>
</rss>

