HANA In-Memory Computing, Licensing and global_allocation_limit

[Former Member]

Hi,

I am new to the HANA word and i have some queries which i am interested to know more about.

1) How the HANA In-Memory computing works, in the sense how it calculates which column table/column/data to be kept in memory and what to be unloaded from the In-Memory.

I have gone through the SAP Admin doc which says the below statement :-

[Under normal circumstances, the SAP HANA database manages the loading and unloading of tables into and from memory independently, the aim being to keep all relevant data in memory.

As the SAP HANA database automatically manages the loading and unloading of tables, you should normally not have to interfere with this process]

These statements only tells me that HANA will do all on its own automatically.

But we wants to know how we can monitor what is happening with our Database- what is moving in and out, how to monitor it or how to get information about it?

2) The next question is on Licensing, what all data elements are covered under license? and can we use global_allocation_limit parameter to be under out license limit? if so

a) what impact will it have on the performance if we use this parameter?

b) which data will it pick to move out from In-Memory?

Thanks & Regards

Sid

[Former Member · Accepted solution]

Please have a look at SAP Note 1999997 where questions like these are discussed.