Choosing The Most Effective Approach for Technical Migration to SAP HANA

There are three main technical migration paths to SAP HANA. All of these methods have their own advantages and disadvantages compared to each other. My aim is to provide guidance and recommendation to plan your HANA technical migration using most effective approach for your business case.

Before starting I have to mention that all these methods (except maybe greenfield approach) would require a general technical planning and preparations such as;

• Housekeeping activities, removing obsolete data or archiving old data.
• Collect and update database statistics
• Perform consistency check for tables and dictionary objects.
• Operating system and database related checks and verifications.
• Parameterization for improved performance.

Managing cold data in SAP HANA database memory

So once you have the cold data moved away from the main memory you will notice that it is re-loaded whenever needed. But for how long will the cold data stay in memory so that the aging still makes sense? This blog explains how cold data is managed in memory and describes different strategies for keeping it all under control.

HANA database takes care of loading and unloading data to and from memory automatically with the aim to keep all relevant information in memory. In most cases only the necessary columns (i.e. columns that are actually used) are loaded into memory on the first request and kept there for later use. For example after system restart only a few columns might be initially loaded into memory and only for the hot partition as shown in the figure below.

S4HANA Basics for a Technology Consultant

“S4HANA”, the new generation business suite has already arrived and am one of the lucky chaps to have a hands-on.

As you know there is lot of material on help.sap.com and SCN to provider a deeper insight on the product, I think I read all of it and want to put everything in this blog.  Well that was sarcasm, in this blog I will summarize my view point as a Technology consultant interested in technology stack and migration paths and scenarios.

Architectural changes:

“If we have many ways to achieve the very same thing, then we lack standardization on the product”
If you want to give me all the credit for the phrase then please....

Well not my words, I picked it form one of the speaker at a conference.  They really make sense.

Many people might disagree with the above statement but the argument I have is, we need to invest in many product which give me same functionality.
S4HANA is re-imaged business suite to re-image your business. SAP say they used  "principle of one" in building S4HANA.