- SAP has made enormous claims around HANA, but data points from the field contradict these claims.
- In this article, we cover one of these case studies versus DB2.
We have been publishing individual case studies for HANA. In each of the case studies, there is information that is in dramatic opposition to what is generally published on HANA.
Here are some direct quotes of someone who reached out to us.
DB2 Stability Versus HANA
We have had DB2 in our environment running SAP for over a decade. It has taken a lot of external damage (power outages, disk loss, hardware failure) and worked like it’s reputation as a tank.
DB2 is not fancy, and IBM has dropped the ball with marketing on this gem, but it just worked. You could sleep at night with it.
We converted our BW system to HANA, in in less than a month, it had 2 corruption bugs.
Data Loss Due to HANA
Sales will often discuss how quickly something can be done. However, what is often left out of the discussion is the repercussions from a change.
We lost an entire month’s worth of data because the corruption was not detected until we restarted the system. Support initially was horrible and even at points contentious with us. Took us 3 days for support to admit there was corruption, and that only happened when our sales rep (who did a great job) got involved. After that, support was great.
For a supposedly flagship product, this was the biggest disappointment and most painful experience of my entire career.
Well, that is quite a statement, but as we have covered in many articles at Brightwork, it is impossible for HANA to meet the sales and marketing claims around it. HANA is a flagship product, but it is still not a mature product.
Forced Conversion to S/4HANA?
We dodged a major bullet. We were able to successfully recover our lost data from our ECC system.
Now SAP is forcing customers to convert to S/4. I cringe at the thought of that given our experience. Digging through the SAP HANA known issues OSS notes, there’s tons of corruption and crashes documented. While I appreciate support’s transparency, it shows how immature this product is.
This is a serious issue as we cannot find a single live S/4HANA instance that we consider real. That is not a S/4HANA instance that is only being used by a consulting company so they can sell S/4HANA services, or an offline test system, etc.. We think that S/4HANA should not even be considered for evaluation until 2022.
SAP’s Database Obsession
“Who buys a product because of the database? It’s the most unsexy part of the entire software stack. It’s just supposed to run and move data in and out AND KEEP IT SAFE.
When I go to Salesforce, or ServiceNow, or any other SaaS provider, do I really care what backend they are using? No, I just want it to work.
Selling points should be on the front end, the business logic.”
Yes, that is true. We covered how SAP overemphasizes HANA in the article How SAP HANA vs TeraData and Tableau Market Backend Technology.
Issues with Aggregation and HANA
“Also, another selling point SAP gave us was that development would be much easier, because a lot of aggregation layers would be stripped out of the process. Guess what, if you go live on HANA from scratch, that may be true, but if you’re a legacy customer, the maintenance of these “Hanatized” objects is actually double the work.
And you know what that Hanatization actually does? It makes it impossible to run those objects on another database. What does that mean? It means vendor lock-in and impossible switching costs.”
Correct. SAP has been silent on the fact that HANA has inconsistency with BW, which is where most of the HANA implementations have been performed. BW was designed to work with a row-oriented database as we cover in the article The Four Hidden Issues with SAP’s BW-EML Benchmark.
The Benefit of HANA Over Sybase?
“The other question is, why couldn’t SAP just give customers an incentive to run their stack on Sybase? That is a mature code base that is robust, Wall Street has run it for decades and it would have been another sleep at night technology I would have been fine with.
SAP could have offered HANA as a premium feature, like they did with BW accelerator or Livecache.”
SAP owns the IQ and ASE database from the Sybase acquisition. However, it deemphasizes the far more mature Sybase databases in favour of HANA. This is true even though IQ is a column-oriented design, which is very similar to HANA.
This case study tells us an interesting story, which is corroborated by other case studies and other research we have performed. As is the norm, the case study shows no connection to the sales and marketing claims around HANA.
Search Our Other HANA Content
Getting to the Detail of TCO
The Mechanics of TCO
- Understand why you need to look at TCO and not just ROI when making your purchasing decision.
- Discover how an application, which at first glance may seem inexpensive when compared to its competition, could end up being more costly in the long run.
- Gain an in-depth understanding of the cost, categories to include in an accurate and complete TCO analysis.
- Learn why ERP systems are not a significant investment, based on their TCO.
- Find out how to recognize and avoid superficial, incomplete or incorrect TCO analyses that could negatively impact your software purchase decision.
- Appreciate the importance and cost-effectiveness of a TCO audit.
- Learn how SCM Focus can provide you with unbiased and well-researched TCO analyses to assist you in your software selection.
- Chapter 1: Introduction
- Chapter 2: The Basics of TCO
- Chapter 3: The State of Enterprise TCO
- Chapter 4: ERP: The Multi-Billion Dollar TCO Analysis Failure
- Chapter 5: The TCO Method Used by Software Decisions
- Chapter 6: Using TCO for Better Decision Making