Symptom
You are using a HANA database either as Suite on HANA or in a
Side-by-Side scenario.
In Report Painter/Writer reports, the performance of reports can still be improved upon.
Observation: In traces, you observe that number of selects for transaction data selection is very high and the number of data lines selected is less thus not leveraging the capabilities for HANA.
Side-by-Side scenario.
In Report Painter/Writer reports, the performance of reports can still be improved upon.
Observation: In traces, you observe that number of selects for transaction data selection is very high and the number of data lines selected is less thus not leveraging the capabilities for HANA.
Other Terms
REPORTWRITER, HANA, SGRW_PERFORMANCE
Reason and Prerequisites
The performance of reports can be significantly improved by selecting
more data lines from HANA in a single selection. However it is observed
that after a certain limit, the more you select the worse is the
performance. So an optimal number of data lines for single select is
taken as 20,000 lines for HANA selection.
Solution
Implement the attached correction.
After you implement the correction instructions, all report groups must be regenerated (see also SAP Note 78109).
Also note that when you turn side by side HANA selection off or on in transaction HDBC to switch between the use of HANA and primary database, each time all the report groups have to be regenerated.
After you implement the correction instructions, all report groups must be regenerated (see also SAP Note 78109).
Also note that when you turn side by side HANA selection off or on in transaction HDBC to switch between the use of HANA and primary database, each time all the report groups have to be regenerated.
No comments:
Post a Comment