I often get comments or e-mails from our readers regarding my articles. As a reaction to another article of mine about the release change from AnyDB to Hana, one SAP partner based in Switzerland told me that I had grossly overexaggerated.
They said that this release change is neither complex nor expensive. For landscapes with 2 systems, the Swiss SAP partner charges 17,000 euros, for 3-system landscapes 22,000 euros, if the Hana servers are operated in the data center of said SAP partner.
The SAP partner wrote to me, “I think that you are describing it as way more complex than it actually is. While there are many uncertainties, variables and obstacles on the long S/4 Hana conversion road, the migration from ERP on AnyDB to ERP on Hana is certainly not one of them.”
Everything the Swiss SAP partner is saying is technically correct. If customers know what they want and what their business needs are, migrating to Hana doesn’t seem as daunting anymore.
Before the Hana migration
What I was talking about in the article, however, wasn’t so much the migration of ERP data from AnyDB to Hana. I was talking more about the evaluation of the different Hana versions and the inevitable deadline 2025.
As I detailed in a different article, many different Hana versions are operated in SAP’s own datacenter. Some versions work well with SAP applications, others don’t. Some are certified for Intel or Power servers, others aren’t. If SAP can’t tame the chaos in their own datacenter, how should customers be able to do it?
But that’s not all! Customers face many more decisions. IBM or Intel? Scale-out or scale-up? Persistent Memory, yes or no?
If SAP customers manage to answer all these and many more questions, then the release change will not be difficult anymore. That much is true. However, that’s not what I was referring to. The Hana database per se is not daunting – but the uncertain, unfinished Hana roadmap is.