As we all know that SAP HANA consumes memory during runtime of report depending on a) modeling is done in HANA (again Gui,SQL Procedures) , BW (7.3 Vs .4), or mixed (both native + BW) b) depending on end-to-end design SAP HANA thru BO (How BO is interacting with HANA, traffic in between, also logic in BO) C) multi-node vs single node - HANA production landscape (scale out vs scale up architecture) The standard quick sizer shows the estimated static memory of HANA is equal to dynamic HANA memory for sizing, in reality it is not sufficient. Especially if the data foot print (after compression) is very less (just take example - 125GB data foot print out of 250GB HANA ), and HANA with 250GB might not support if the users are running multiple concurrent reports with complex native modeling. There are various scenarios mentioned in above could also contribute the overall HANA sizing. There are no standard document take into consideration during the sizing to convince the customer about the requirement of HANA dynamic memory vs showing quick size in HANA per SAP provided documentation. i appreciate help from SAP referencing the documentation as customers need authentic information regarding dynamic memory prospective as this is important factor in sizing needs and to make successful production implementations in HANA. Thanks Ravi Appala
↧