The objective of this SAP HANA Under The Hood series is to provide some insights on particular SAP HANA topics. Like a mechanic, look under the hood and take apart a piece to examine its functioning.
I know there is already very good blogs on this topic, The purpose of this blog is to explain the process of performing a simple homogeneous system copy of a HANA (MDC-multi tenant database container) based system using the recovery of the source backup on the target HANA DB using HANA Studio and Using SWPM , I don’t find More blogs and details regarding homogeneous system copy or backup/Restore on HANA 2.0 on multi tenant database container.
Many people heard about data aging in context of HANA. You see it on a lot of SAP slides with DLM (Data Lifecycle Management) or in BoH / S/4HANA context, books about HANA and especially in the result of the HANA ABAP sizing reports. In my opinion the naming here – “clean-up” – is a little bit misleading. It is a bit more than just housekeeping and lot of things you have to pay attention to.
If you successfully finished my last blog post about data aging ‘General Iinformation about data aging’ it is time for the deep dive. How SAP has implement it and how it works in detail.
As you already have read partitioning is an elementary part of data aging process to separate the current from the historical. Therefor range partitioning is used with an additional column called ‘_DATAAGING’:
HANA 2.0 SPS 02 is now available and there have been a number of important updates to the predictive analysis library (PAL). The focus is on ease-of-use rather than introducing a bunch of new algorithms (though there are a couple).
In this blog I’ll introduce the updates and show you where to find hands-on tutorial videos:
Many people heard about data aging in context of HANA. You see it on a lot of SAP slides with DLM (Data Lifecycle Management) or in BoH / S/4HANA context, books about HANA and especially in the result of the HANA ABAP sizing reports. In my opinion the naming here – “clean-up” – is a little bit misleading. It is a bit more than just housekeeping and lot of things you have to pay attention to.
In this exercise, I’ll give a walkthrough on how to perform a top down investigation on high & peak HANA memory usage and its associate top memory consumers with the aid of HANA SQL scripts attached to SAP Note 1969700 – SQL Statement Collection for SAP HANA and Statistics data (History / Current) collected by ESS / SSS (Mandatory. Recommended retention = 49 days)
I’m taking below example where I was asked to perform a memory analysis on a productive system where there was a spike of peak memory usage, around 5.9TB.
BW on HANA can easily enable SQL data access for third party tools, using the “External SAP HANA View” flag to automatically generate Calculation Views out of BW objects. However, Consuming multidimensional BW scenarios through relational SQL paradigm can lead to quite some issues with performance. This blog is about a few basic technical tips, which help to enhance runtime performance. Tested with BW 7.5 on HANA SPS 10, 11 and 12.
S/4 HANA stands for Simple 4th Generation Business suite solutions from SAP which will run on SAP HANA. SAP HANA is one of the preferred product among the companies seeking for an optimized enterprise solution because the product has come a long way from its previous predecessors which had its transaction processing and analytical processing in different platforms, that meant more time on data output and decision making.
It is very well known as The Next Generation Business Suite and it is greatest innovation since R3 and ERP from the SAP world. It unites the software and people to build businesses to run on real-time, networked and in simple way. It has got built-in analytics for hybrid transactional and analytical applications.
Many people still think all data in HANA which exists in the data area also loaded into memory all the time. Of course there are some techniques which influence the unload / placement of tables e.g. data aging and the non-active data concept of BW. Usually unloads happen based on a “least recently used” (LRU) approach, so the columns having not being used for the longest time are unloaded first. So HANA decides when it makes sense to unload some tables to free memory.
But what about your own tables? Can you also take influence when data are unoaded? For general information you can refer to 2127458 – FAQ: SAP HANA Loads and Unloads. Ok you can manually unload or load tables. But you want to do this automatically and want to understand when tables are loaded or unloaded.
This document will deal with issues regarding analytical privileges with SAP HANA.
So what are Privileges some might ask?
System Privilege:
System privileges control general system activities. They are mainly used for administrative purposes, such as creating schemas, creating and changing users and roles, performing data backups, managing licenses, and so on.
Whilst importing delivery units into your HANA System you can sometimes run into some common errors which can easily be fixed without the means of opening a SAP Incident.
Lets look at an example.
Here you are importing SAP HANA Analytics into your system. During the import you see an error: