Can You Take and Pass the HANA Challenge?

Executive Summary

  • We have devised one of the most difficult challenges in all of IT.
  • To pass it, one must write out the claims made by SAP on HANA.


SAP made many claims about HANA, and one of the most inaccurate was that HANA was not only a database but so many other unrelated items. Therefore we decided to create this challenge.

  1. A database, and zero latency at infinite load. 
  2. A platform
  3. A development environment
  4. A cloud offering
  5. A cloud development environment
  6. An advanced planning system (don’t question it Pedro — but HANA was slated to replace APO – which would be the first application ever replaced by a database in human history)
  7. A Big Data platform
  8. An entirely new application architecture.
  9. A coffee maker
  10. A popcorn machine

I have been laughing heartily as I have been writing this.

Everything listed above (except the coffee machine and popcorn maker) are real SAP claims.

You cannot repeat the claims made by the HANA crowd and have any background in software and databases and not begin laughing. Just try to type out the claims.

But it does not stop there. As pointed out by Rolf Paulsen, HANA was not only a database but multiple database “types”, which Rolf accurately lists as the following:

  1. 1a. A relational database for all OLAP use cases
  2. 1b. A relational database for all OLTP use cases
  3. 1c. A NoSQL database
  4. 1d. A graph database
  5. 1e. A geospatial database

Typing this all out without being seized by the natural compulsion to laugh is what we call the “The HANA Challenge.”

Taking Responsibility for Lying to Your Clients

Something that really needs to be discussed is how wrong so many people were on HANA. We covered this in the article Who Was Right and Who Was Wrong on HANA?

Now is an excellent time for all of those that had no idea what they were talking about or lied for SAP to so many customers to come clean and admit it. You can look in the mirror and repeat three times.

“I am a parrot for SAP.”

“I repeat things I don’t know are true.”

Who Needs To Do This?

That includes Gartner, Accenture consultants, Forrester, the list is quite long.

The HANA Fiasco is not just a matter of not HANA not meeting its performance claims; this is one of the most ridiculous proposals in enterprise software history. I am going to reach out to the Computer History Museum in Mountain View to get HANA listed somehow. Future generations have to know what happened. And we have the quotations documented.

Search Our Other HANA Content

Financial Disclosure

Financial Bias Disclosure

Neither this article nor any other article on the Brightwork website is paid for by a software vendor, including Oracle, SAP or their competitors. As part of our commitment to publishing independent, unbiased research; no paid media placements, commissions or incentives of any nature are allowed.

HANA & S/4HANA Research Contact

  • Interested in Research on S/4HANA & HANA?

    It is difficult for most companies to make improvements in S/4HANA and HANA without outside advice. And it is not possible to get honest S/4HANA and HANA advice from large consulting companies. We offer remote unbiased multi-dimension S/4HANA and HANA support.

    Just fill out the form below and we'll be in touch.


TCO Book



Enterprise Software TCO: Calculating and Using Total Cost of Ownership for Decision Making

Getting to the Detail of TCO

One aspect of making a software purchasing decision is to compare the Total Cost of Ownership, or TCO, of the applications under consideration: what will the software cost you over its lifespan? But most companies don’t understand what dollar amounts to include in the TCO analysis or where to source these figures, or, if using TCO studies produced by consulting and IT analyst firms, how the TCO amounts were calculated and how to compare TCO across applications.

The Mechanics of TCO

Not only will this book help you appreciate the mechanics of TCO, but you will also gain insight as to the importance of TCO and understand how to strip away the biases and outside influences to make a real TCO comparison between applications.
By reading this book you will:
  • 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