SAP Solution: Hana 2

The development of the Hana database was planned by Professor Hasso Plattner and former Chief Technology Officer Vishal Sikka as a metamorphosis: Development from egg to sexually mature animal via independent larval stages. Ex-chief technology officer Bernd Leukert then had to present Hana 2 in 2016.

According to a promise by Hasso Plattner, these lines should not exist. At the presentation of Hana, he and the then Chief Technology Officer Vishal Sikka explained that there would never be version numbers for Hana because the database is continuously being developed.

SAP has a long-known behavioral disorder: impatience. No sooner has a new idea been born than the existing customer is expected to license it. Corrections and bug fixes then happen during operations.

With the introduction of Hana 2, the path to S/4 for existing SAP customers has become even more challenging. In this exclusive interview with E-3, Hinrich Mielke, Director of SAP at Alegri, outlines the advantages and disadvantages of possible changeover scenarios.

"Usually, when people hear just words, they think there must be something to think about." I think nothing when I hear SAP CEO Bill McDermott talk about "run simple".

The last will be the first. The last R/3 users who customize the promised Hana beyond 2020 will get a mature, stable version X. Everyone else is a guinea pig.

After importing the latest Support Package Stack (SPS), Hana reports to the existing customer with, "The doomed greet you!"

When Professor Hasso Plattner and former Chief Technology Officer Vishal Sikka presented the "revolutionary" Hana many years ago, the message was: no version numbers, eternal compatibility, never again release changes.

SAP seems to want to suspend the laws of economics: You eliminate your own innovations and try to overtake yourself - to the detriment of existing customers and the community.

New in-memory platform to make SAP fit for digital transformation and help companies bridge the gap between agility and stability.