We are happy to announce via SAP Partner Press Release that our IT-Conductor Cloud-based Application Management solution is now available for online purchase on the SAP Store.

 Setting up Scale Out, High Availability and Monitor HANA

HANA scale out is unlike other database platforms, it can be simple but complex at the same time.  Depending on the scenario, the in-memory nature of HANA services, the persistence layers and optional multi-tenancy (

In a prior blog we provided some tips on Managing HANA memory. In this article we will further explore the improvement with ESS (Embedded Statistics Service) available on HANA from SPS 7 revision 74 or higher. As a quick recap, memory consumption by the hdbstatisticsserver can be heavily impacted by the volume and frequency of various statistics collected by the HANA statistics engine, mainly the columnar tables in _SYS_STATISTICS schema. These tables provide stats for monitoring by tools such as the HANA Studio, SAP DBA Cockpit and Solution Manager, as well as external SAP management tools like IT-Conductor and HANA Management Pack for SCOM.

We've had the opportunity to work with HANA both as a Startup porting our application to HANA as well as with our SAP customers running HANA in production scale BW or ECC environments. In the R&D environment we have limited hardware capacity and thus resources, especially memory is always a constraint, so we learnt ways to monitor, and automate to optimize our performance and use of the system. In the customers' production environment, we have seen original architecture plans double in nodes and/or memory before they even got to performance testing phase.

Here are a few simple tips to manage the memory and space (which affects memory consumption) in HANA: