Hana's light and shadow

On the one hand, innovations bubble up, on the other hand, Hana does not achieve sufficient stability. For operational use, however, stability counts more than innovation.

It's all well and good that persistent memory is now available for Hana, but many experts from the SAP community think: solution seeks problem! Who needs persistent memory? In which scenarios does this Intel innovation bring real added value for existing SAP customers?

The situation around Hana is tense and critical. The discourse between a Hana expert and SAP shows the full extent: [...] As long as SAP releases a new patch every six weeks and changes the recommendations for the parameter settings even more frequently, persistent memory makes sense, doesn't it?

And the SAP answer from the office of CEO Christian Klein: [...] Both updates and booting through are decisions of the customer - the update frequency is his decision alone. Most Hana parameters can be changed online - without restarting [...].

Which led to the following SAP community statement: Is actually quite an indictment of what is coming out of the office of an SAP executive. "Updates as well as booting through are decisions of the customer - the update frequency is his decision alone."

Why does SAP release a patch with nice regularity, if not for customers to install it, to fix detected bugs, which partly falsify the result of calculations (who can still trust his system?) and again and again memory leaks, which cause the system to go to pieces at regular intervals!

And if you escalate to the support, they say of course: "Patch them first to the current state, before we even look at the matter". The Early Watch Report has been showing bright red lights for a long time anyway!