While working with big clients having businesses throughout the globe, it becomes really important to manage the data and wherever possible, reduce the data base size. When dealing with millions of records, we often come up with a situation where the data base size reaches almost the maximum capacity and data loading is no longer possible. We always cannot ask client increase the DB size as lot of money is involved. Especially if you are using HANA data base. Several Archiving techniques have been introduced in HANA like NLS and Dynamic Tiering for Using Extended Tables, but these are not only expensive but have some restriction. For example if a document is already achieved using NLS, then if you want to load delta of that record into DSO, you will come up DSO activation error.
We have a simple technique that can be used easily to reduce main memory size without incurring too much of implement cost. Here we are storing the not so important data in separate memory called Corporate Memory.
First we need to analyze which are the large tables in DBACOCKPIT. Then we need to take decision based on business requirement which data is not so important. Data are classified into 3 types: Hot, Warm and Cold
Hot Data: Data which is regularly used and often changed e.g. Last 3 years of data
Warm Data: Data which is rarely used and may need once or twice in a quarter e.g. Data between year 2012 and 2006.
Cold Data: Data which is most likely never going to be used but still business wants to keep e.g. data beyond 2006.
The production data can be classified into these groups based on business requirement. The selection filed can be time or company code or anything. It should be purely a business decision.
With corporate memory we intend to keep both Warm data and Cold data out of main memory and thus reduce drastically the size of main memory
Create Inflow DSO which will be copy of the large BW tables.
To understand the advantages of corporate memory, we first need to understand how the data is stored in the HANA data base.
When a data is loaded into an Info Provider in HANA, it actually gets loaded into two storage area: Memory and Disk. Thus a data will be accessed very quickly since it resides in memory like RAM.
The screen shot suggests that it has got two Memories:
Current total Memory and Size on disk
With Corporate memory concept, we can offload some of the data from Main memory and keep it only in disk, so main memory size gets reduced
Unload "SAPMIW"."/BIC/B0002683000"
Let’s take an example of FI DSO. We assume that it has data from year 2000 to 2015.
Business approved that Data form 2012 onwards will only be useful for reporting and rest are historical data and may not require often. Hence Data from year 2000 to 2011 can be considered as Cold and Warm data. Hence these may not be required to be kept in Maun memory. These data we will be stored in Inflow DSO and then will be removed from the Main DSO.
Unload "SAPMIW"."/BIC/AFIXXXXX" (Here /BIC/AFIXXXXX is the active table of Corporate DSO)
After taking the statistics from the cockpit, we need to do these below simple steps
Unload "SAPMIW"."/BIC/AFIXXXXX"
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
54 | |
5 | |
4 | |
4 | |
4 | |
4 | |
3 | |
3 | |
3 | |
3 |