topic Re: Performance Analysis in Application Development and Automation Discussions https://community.sap.com/t5/application-development-and-automation-discussions/performance-analysis/m-p/2999658#M708618 <HTML><HEAD></HEAD><BODY><P>Hi</P><P></P><P><A class="jive_macro jive_macro_thread" href="https://community.sap.com/" __jive_macro_name="thread" modifiedtitle="true" __default_attr="631728"></A></P><P></P><P><A class="jive_macro jive_macro_thread" href="https://community.sap.com/" __jive_macro_name="thread" modifiedtitle="true" __default_attr="631728"></A></P><P></P><P>In connection with SELECT ... FOR ALL ENTRIES the following problems occur:</P><P>1)You cannot have an empty internal driver table. If the driver table is empty, selection is not limited. In particular, WHERE clause conditions are not evaluated if they do not refer to the internal driver table. </P><P>2)Duplicate table entries should be deleted from the internal table before executing the SELECT... FOR ALL ENTRIES. If they are not deleted, identical data is read unnecessarily from the database.</P><P>&lt;b&gt;3)The parameter rsdb/max_blocking_factor must be implemented according to SAP's database-specific recommendations&lt;/b&gt;.</P><P></P><P></P><P>&lt;b&gt;Reward if usefull&lt;/b&gt;</P></BODY></HTML> Tue, 13 Nov 2007 09:03:18 GMT Former Member 2007-11-13T09:03:18Z Performance Analysis https://community.sap.com/t5/application-development-and-automation-discussions/performance-analysis/m-p/2999657#M708617 <HTML><HEAD></HEAD><BODY><P>Hi,</P><P></P><P>Can someone tell me what is meant by rsdb/max_blocking_factor?</P><P>And how do we calculate the above mentioned factor?</P><P></P><P>Thanks,</P><P>Supriya Manik.</P></BODY></HTML> Tue, 13 Nov 2007 08:49:19 GMT https://community.sap.com/t5/application-development-and-automation-discussions/performance-analysis/m-p/2999657#M708617 Former Member 2007-11-13T08:49:19Z Re: Performance Analysis https://community.sap.com/t5/application-development-and-automation-discussions/performance-analysis/m-p/2999658#M708618 <HTML><HEAD></HEAD><BODY><P>Hi</P><P></P><P><A class="jive_macro jive_macro_thread" href="https://community.sap.com/" __jive_macro_name="thread" modifiedtitle="true" __default_attr="631728"></A></P><P></P><P><A class="jive_macro jive_macro_thread" href="https://community.sap.com/" __jive_macro_name="thread" modifiedtitle="true" __default_attr="631728"></A></P><P></P><P>In connection with SELECT ... FOR ALL ENTRIES the following problems occur:</P><P>1)You cannot have an empty internal driver table. If the driver table is empty, selection is not limited. In particular, WHERE clause conditions are not evaluated if they do not refer to the internal driver table. </P><P>2)Duplicate table entries should be deleted from the internal table before executing the SELECT... FOR ALL ENTRIES. If they are not deleted, identical data is read unnecessarily from the database.</P><P>&lt;b&gt;3)The parameter rsdb/max_blocking_factor must be implemented according to SAP's database-specific recommendations&lt;/b&gt;.</P><P></P><P></P><P>&lt;b&gt;Reward if usefull&lt;/b&gt;</P></BODY></HTML> Tue, 13 Nov 2007 09:03:18 GMT https://community.sap.com/t5/application-development-and-automation-discussions/performance-analysis/m-p/2999658#M708618 Former Member 2007-11-13T09:03:18Z