on 03-04-2008 1:06 PM
Is it possible to temporarily override, by session, this parameter? I want to gauge its effect on performance, but I don't want to change the master setting.
For instance, in Oracle, it is possible to temporarily change a setting at the session level with the 'ALTER SESSION' command.
Is there something similar for this parameter?
Hi Jerry,
better than changing the parameter for the hole system, even temporarily, is to switch it for a single statement. You may do this with a hint. This is the minimal impact scenario possible. Please have a look to note #48230.
Best regards
Ralph
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Jerry,
The parameter rsdb/max_in_blocking_factor is a dynamically switchable parameter which you can change any time going to T-Code RZ11. But as suggested by SAP we should not change the values of this parameters.
Parameter : rsdb/max_in_blocking_factor
Short description: Max. split factor for FOR ALL ENTRIES queries
Parameter description :
This parameter is for internal use only and must never be
changed without the prior consent of SAP.
An internal table [itab] with input data is always transferred in
case of an ABAP SELECT request with the addition FOR ALL ENTRIES.
In the same way as rsdb/max_blocking_factor, this parameter
specifies an upper limit for the number of entries of [itab] to be
processed, in case the actual statement is mapped to an IN clause
(see rsdb/prefer_in_itab_opt).
In the same way as rsdb/max_blocking_factor, the blocking factor
limit is used instead of rsdb/max_in_blocking_factor, if the upper
limits of the database system would otherwise be exceeded.
Best Wishes.
Kumar
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.