How Accurate Was Hasso Plattner About SAP HANA Publications?

Executive Summary

  • At SAPPHIRE 2019, Hasso Plattner makes claims around academic publications supporting HANA.
  • We evaluate the accuracy of these claims by fact-checking the publications.


This is the video of Hasso Plattner we will be reviewing for accuracy.

The Hasso Plattner SAPPHIRE 2019 Video on Peer Reviewed Publications for HANA

The 200+ Peer-Reviewed Articles on HANA?

This claim immediately struck as odd. Every other claim in this slide is also not true. But we will focus on the peer review claim.

We immediately suspected this claim, one reason being that Hasso tends to lie all the time, but also HANA is not a popular enough database to have so many publications that cover it as a topic. 

Hasso quickly transitions to S/4HANA in the next slide. Each of these claims is wildly false. 

  1. SAP report 11,000 customers, but these are license holders. S/4HANA has almost no real customers that are live on S/4HANA. This may seem shocking, but once you move past the customers that are SAP consulting companies that implemented the application for marketing reasons and use S/4HANA Cloud (which in most cases is not actually used by the consulting firm), it becomes very difficult to validate any live S/4HANA customers. Virtually every S/4HANA implementation up to this point has failed.
  2. S/4HANA performs slower in material planning than ECC on Oracle, as we covered in the article HANA as a Mismatch for S/4HANA and ERP. Therefore 20x performance is impossible.
  3. HANA will reduce a previous production database supporting ECC by roughly 30 to 35%. This has come from many data points reported to us from the field, as we covered in Is Hasso Plattner and SAP Correct About Database Aggregates?
  4. SAP would not have any idea if S/4HANA improves productivity, because almost no one is using S/4HANA outside of test systems.

But the problem here, and it is a hugely significant problem, is that Hasso makes it sound as if these assertions are the conclusion of the 200+ peer-reviewed papers on HANA. If our contradiction is wrong, then the 200+ studies will clearly show that these are the average values where this extensive and peer-reviewed measurement of HANA benefits was performed. According to Hasso, the assertions of both slides are supported by these 200+ academic/peer-reviewed publications.

So do they? Let’s find out.

Our Analysis of the Peer Reviewed Publications on HANA

The number of peer-reviewed publications can be found by using academic search engines. Using such engines will not capture all of the articles in an area, but it will normally catch most of them. These were the publications that we could find. We evaluated them by where the author’s worked and whether they supported the claims made by Hasso Plattner in his speech.

Publication #1: SAP HANA als Anwendungsplattform für Real-Time Business

  • Author(s): This publication was written by P. Prassolb.
  • Author Affiliation: P. Prassolb was employed by SAP at the time of this publication.
  • Does the Paper Support Hasso’s SAPPHIRE Assertions?: No. Nowhere does the paper support any of the information published in the two slides in Hasso’s presentation.
  • Can this be Counted as a Publications About HANA?: Yes

Publication #2: Managed Query Processing within the SAP HANA Database Platform

  • Author(s): Normal May, A. Bohm, M. Block and W. Lehner
  • Author Affiliation: P. the first three all worked for SAP at the time of publication. The employment of W. Lehner is unstated.
  • Does the Paper Support Hasso’s SAPPHIRE Assertions?: No. The paper has nothing to do with measuring the benefits of HANA or S/4HANA.
  • Can this be Counted as a Publications About HANA?: Yes

See the following quote from the publication.

“As a common abstraction layer for all these interfaces, we have defined the Core Data Services (CDS). In particular, the CDS is used for defining semantically rich domain data models which can be further enriched through annotations.”

This publication is not a research paper of any kind but is a more detailed version of an SAP marketing document. There is no hypothesis proposed and nothing tested. It is a listing of HANA’s technical offerings. It is unclear why this document was ever published in a journal.

Publication #3: Predictive Analytics in Marketing Mit Moderner Systemarchiteckture

  • Author(s): This publication was written by Jan Matthes.
  • Author Affiliation: Jan Matthes was employed by SAP at the time of publication.
  • Does the Paper Support Hasso’s SAPPHIRE Assertions?: No. Nothing Hasso states in the SAPPHIRE presentation is even discussed in the paper.
  • Can this be Counted as a Publications About HANA?: Yes

The paper’s synopsis includes the following description.

“This article addresses the in memory platform of SAP HANA. First it is being illustrated why SAP HANA is indeed a real platform. Subsequently, it is being explained to what extent SAP HANA can be seen as an innovative technology, what the differences to existing systems are and which opportunties are being offered to transform the technical capabilities of the platform into new business models and commerical success…the advantages of the in-memory technology compare to conventional disc-based databases are being examined. Furthermore column-based data storage, parallelization and the overcoming of the traditional separation of transactional and analytical data management are being discussed.”

These are all of the same claims made by SAP marketing, and also does not appear to be a research paper at all, but is a marketing document that was somehow pushed through a peer-reviewed journal.

Publication #4: Evaluation of in-memory storage engine for machine learning analysis of security events

  • Author(s): This publication was written by Andrey Sapegin, Marian Gawron, David Jaeger, Feng Cheng, and Christoph Meinel.
  • Author Affiliation: Andrey Sapegin worked at SAP at the Hasso Plattner Institute at the time of the publication. The employment affiliation of the other authors is not listed. But a later paper #12 in this list, lists all the authors (but one) as employed at the Hasso Plattner Institute.
  • Does the Paper Support Hasso’s SAPPHIRE Assertions?: No. The entire focus of this paper is security. Therefore, it cannot be the source of the information provided by Hasso Plattner in his 2019 SAPPHIRE presentation.
  • Can this be Counted as a Publications About HANA?: Yes

Publication #5: CancerLinQ Advancing Quickly

This is a one-page article in the Oncology Times. This appears to be some promotional insert. The only reference to HANA is the following.

“…CancerLinQ LLC, now has teamed with the software manufacturer SAP to use the SAP HANA platform to develop CancerlinQ.”

It is difficult to understand how this is a peer-reviewed article.

  • Can this be Counted as a Publications About HANA?: No

Publication #6: Design Thinking

  • Author(s): This publication was written by Christoph Meinel and Julian von Thienen.
  • Author Affiliation: Christoph Meinel and Julian von Thienen both work for the Hasso Plattner Institute.
  • Does the Paper Support Hasso’s SAPPHIRE Assertions?: No. HANA is barely mentioned in the article, and the article is about Design Thinking.
  • Can this be Counted as a Publications About HANA?: No

Publication #7: Big Data: Herausforderungen und Potenziale für deutsche Softwareunternehmen

  • Author(s): This publication was written by Dr. Stephan Fischer
  • Author Affiliation: Stephan Fischer worked at SAP at the time of the publication.
  • Does the Paper Support Hasso’s SAPPHIRE Assertions?: No. Hasso’s claims are unrelated to Big Data.
  • Can this be Counted as a Publications About HANA?: Yes

Publication #8: Graph Processing Using SAP HANA: A Teaching Case

  • Author(s): This publication was written by Mark Hwang.
  • Author Affiliation: Mark Hwang was employed at Central Michigan University at the time of publication.
  • Does the Paper Support Hasso’s SAPPHIRE Assertions?: No. This paper has to do with using HANA as a graph database, which in 3+ years of researching HANA is the first time this topic has come up. It is not a paper that has anything to do with Hasso’s claims.
  • Can this be Counted as a Publications About HANA?: Yes

The following quote is from this paper.

“The purpose of this teaching case is to develop a hands-on exercise on graph processing using a hybrid system. The paper provides a background on graph databases and how graph processing is supported in a hybrid system, SAP HANA. It also details step-by-step instructions on how to create, modify, and process a graph database using SAP HANA. The teaching case provides instructors with materials that can be readily implemented in classrooms.”

The paper contains false statements about HANA which have clearly have been copied and pasted from SAP marketing.

“In recent years SAP developed its proprietary in-memory database known as SAP HANA, which underpins a technology platform that supports real-time enterprise transactional and analytical processing.”

Publication #9: An In-Memory Approach to Sentiment Analysis Based on SAP HANA

  • Author(s): This publication was written by Karl Kurbel, Dawid Nowak, Florian Jätzold, and Pavlo Glushko.
  • Author Affiliation: None of the authors worked for SAP at the time of publication. Although the do thank Niraj Singh and Frank Finkbohner from SAP AG “for their support and assistance with this project.”
  • Does the Paper Support Hasso’s SAPPHIRE Assertions?: No. This paper has to do with a sentiment algorithm for analyzing social media. It is not a paper that has anything to do with Hasso’s claims.
  • Can this be Counted as a Publications About HANA?: Yes

Publication #10: Improving Business Intelligence Applications by Using New Generation of Web and Mobile Technologies

  • Author(s): This publication was written by Mihaela-Laura IVAN.
  • Author Affiliation: Mihaela-Laura IVAN was employed SAP at the time of the publication.
  • Does the Paper Support Hasso’s SAPPHIRE Assertions?: No. This paper is focused on showcasing HANA’s features. It is not a paper that has anything to do with Hasso’s claims.
  • Can this be Counted as a Publications About HANA?: Yes

This paper is also filled with SAP marketing claims.

“There are presented the many advantages of which the final user can benefit, such as: fast performance when querying a request, data modelled with the last database innovation of SAP, SAP HANA database, which brings the biggest feature which is in-memory processing. This in-memory computing of SAP HANA enables people to focus on innovation.In the third section are described two examples of web and mobile applications developed with these technologies.

SAP Fiori comes with modern design for a rediscovereduser experience. SAP Fiori user experience (UX) represents a personalized user experience formulti-devices, responsiveness interfaceand with deployment options.When combined with the power of the SAP HANA platform, SAP Fiori provides exclusive responsiveness. SAP Fiori UX is used for enterpriseappsacross the mostbusiness scenarios.”

The overall study is a marketing document made to look like a research paper.

Publication #11: Sap Hana And Its Performance Benefits

  • Author(s): This publication was written by Timur Mirzoev.
  • Author Affiliation: Timur Mirzoev is listed as both a professor at Georgia Southern University and a systems engineer at Lockeed Martin at the time of publication.
  • Does the Paper Support Hasso’s SAPPHIRE Assertions?: No. This paper has to do with when HANA can have its in-memory capabilities leveraged. It is not a paper that has anything to do with Hasso’s claims.
  • Can this be Counted as a Publications About HANA?: Yes

Publication #12: Towards a system for complex analysis of security events in large-scale networks

  • Author(s): This publication was written by Andrey Sapegin, David Jaeger, Feng Cheng, and Christoph Meinel.
  • Author Affiliation: This is nearly the same team of authors that wrote the 4rth paper on this list, and all of the authors worked for the Hasso Plattner Insitute at the time of this publication.
  • Does the Paper Support Hasso’s SAPPHIRE Assertions?: No. As with the previous paper by these authors, this paper has to do with security. It is not a paper that has anything to do with Hasso’s claims.
  • Can this be Counted as a Publications About HANA?: Yes


When Hasso Plattner made the statement about 200+ peer-reviewed publications, was lying about both the number of publications about HANA, as well as the content of those publications.

  • There are not 200+ publications on HANA, there are perhaps ten. (publication #5 is not a research paper but an insert, and publication 6 is not related to HANA, but to design thinking)
  • Not only do nothing in the HANA peer-reviewed publications support anything that Hasso asserted in the SAPPHIRE 2019 presentation, only around 1/2 of the publications even qualify as research.
  • Seven of the ten papers that qualify as actually about HANA were published by authors who work for either SAP or the Hasso Plattner Institute. This means the independence is reduced as to who authored peer-reviewed papers on HANA. The results of any paper written by an employee of SAP will naturally be positive. Furthermore, Hasso misrepresented the peer-reviewed papers that do exist (the ten) by saying that the Hasso Plattner Institute reviewed the papers published on HANA – clearly indicating that the publications were written by others unassociated with SAP. This would be like Brightwork Research & Analysis saying that we reviewed 150 papers which showed that the agreed with our views on subject XYZ, when we wrote most of the articles that we reference as “external articles,” and we simply reviewed our own articles. This is the absolute upper bar of deception.
  • And in addition to Hasso Plattner’s conclusions being entirely manufactured, it calls into question the legitimacy of the Hasso Plattner Institute, as they don’t appear to understand that for example, a published paper is supposed to include a hypothesis, not simply a listing of product features of an item that your employer would like to sell.

Hasso’s claims around his assertions being supported by 200+ peer-reviewed publications is why the Golden Pinnochio Award was created. And he gets one here. 

This presentation by Hasso Plattner is the continuation of a long-term pattern of attempting to the cloak marketing around HANA and S/4HANA in the legitimacy of academic research. Hasso Plattner misrepresents his honorary doctorate as a “real” doctorate as we covered in Does SAP’s Hasso Plattner Have a PhD? He has a ceremonial title as a fake professor of computer science at the Hasso Plattner Institute, which is as an academic impossibility as he has no degrees in computer science, much less a PhD in computer science. At SAPPHIRE 2019 Hasso graduated to referring to non-existent research, only exaggerating the number of peer-reviewed HANA papers by 190+, even the ten papers that exist not only don’t support his assertions at SAPPHIRE, but they are also not even related to his assertions. This was done in an attempt to sell more HANA and S/4HANA.

All of this is thoroughly disreputable behavior. But also completely unsurprising. None of Hasso Plattner’s numbers on any topic is reliable and he is willing to make up any number he needs to try to prove a point.

It is also encouraged by SAP and is ignored by nearly all SAP resources.

*Through the assistance of some people who reached out, more articles were added to the analysis than my initial search engine found.

A Resistance to Criticize Obvious Lies by SAP

This statement by Hasso Plattner was made quite publicly, was widely reported, yet even though it was completely false, no entity that follows SAP reported on this.


A Consistent Pattern of Lying

After many years of analyzing sap in one of the few full-time SAP analysts, the amount of inaccurate information that comes out of SAP it is a consistent theme. And these lies are accepted by SAP proponents for obvious reasons. Actually, beyond acceptance, these lies are most often repeated.

Should SAP Be Immune from Charges of Lying

This does bring up the question of whether SAP should be considered immune from charges of lying.

  • That is is SAP in a special category of company.
  • That large company should never be held to what is true because being large means they have natural authority, and that authority should not be questioned.
  • SAP is German. And German companies don’t lie.

That is should we accept that SAP has the right to lie as much as it seems necessary to meet its objectives and should not be criticized.

Are Lies Part of Capitalism?

I bring up this question because in a recent discussion with an SAP proponent I was told that in a capitalist system it should be expected that software vendors will exaggerate.

It has been proposed to me that lying is ok if it is within a capitalist system. It is unclear as to whether lying is considered a part of communism. According to some, we have to accept lying if we want to participate in capitalism. And it implies that lying is acceptable depending upon the economic system that a country chooses. 


However, SAP exaggerates far more than other software vendors, and I have the evidence to prove this which anyone can see at A Study into SAP’s Accuracy. This is the most comprehensive listing of SAP’s accuracy documented. When we ask SAP proponents to provide their research into SAP’s accuracy, they disappear.

I know quite a few software vendors that while they certainly present their product in the best possible light do not so consistently lie about their product as SAP, which is why we rate them in the bottom of vendor accuracy in our Honest Vendor Ratings. And of course, all of these software vendors operate within a capitalist system as well. But this research tells a different story of SAP’s lying. It illustrates that SAP’s lying is out of line with the lying of other vendors in scale and scope. This should not be seen as a blanket endorsement of other vendors, which is why we created the ratings for a reasonable number of vendors and rated each individually. This research both in the accuracy of other vendors and in a great deal of detail into SAP, allows us to say that SAP lies at a far higher level than the majority of software vendors.

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.

Search Our Other Hasso Plattner Content


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

How Accurate is the Hasso Plattner Institute’s Course Explanation?

Executive Summary

  • The Hasso Plattner Insitute has curious course explanations.
  • We review the accuracy of these descriptions.


The In Memory course offered by the Hasso Plattner Institute was recommended to us to understand in-memory computing. This was recommended to us even though we wrote the article How to Understand Why In-Memory Computing is a Myth and have observed and proven it is a deliberately misleading term.

In this article, we will analyze the accuracy of the description of the in-memory course offered by the Hasso Plattner Institute.

The Quotations

Course Description

“Week 1: The first week will give you an understanding of origins of enterprise computing. It is vital to know the historic development which lead to the emergence of current hardware as we know it now in order to understand the decisions made in the past. Many characteristics of current applications, like materialized aggregates and a reduction of detail in the stored information, have their roots in the past. While these measures were helpful in former systems, they form an obstacle which has to be overcome now in order to allow for new, dynamic applications.”

It is only the Hasso Plattner Institute that thinks this is true. An aggregate is a table of precalculated values. Hasso Plattner is very much opposed to aggregates. However, the reason he gives seems to be directed around making HANA seem to be less expensive than it is. This is because HANA is alone among databases being priced per GB. Aggregates take up space in the database, but they serve a valuable purpose. Without aggregates, constant recalculation is required. Hasso Plattner has stated that this is highly advantageous, but is it? What if those values very rarely change, such as a table of weight conversions? But this table must constantly be recalculated on the fly? If not some rule of excellence has been violated?

Hasso Plattner has stated compression values that have not born out to be true. This is covered in the article Articles that Exaggerate HANA’s Benefits.

Most HANA accounts can expect footprint reductions in the area of 30%. However, this is immaterial to companies as storage is extremely inexpensive, particularly disk storage. John Appleby, SAP proponent and head of an SAP consulting company, has made the statement that disks are a problem because they “take up a lot of space,” which is a claim we analyzed in the article What Was John Appleby’s Accuracy on Moving BW to HANA?

  • The long and short of it is that nothing Hasso Plattner has ever said about database aggregates has made any sense.
  • The focus on aggregates is a gimmick, designed to confuse the message receivers as to what is important in database management.
  • The entire aggregate discussion is a distraction.

“Week 2: Within the second week, the differences between a horizontal, row-oriented layout and a columnar layout are discussed. Concepts like compression and partitioning are introduced. Based on that, you will get an explanation of the internal steps performed inside the database to carry out the fundamental relational operations insert, update and delete. The week concludes with a fundamental difference of SanssouciDB to most other databases: the insert only approach. Following this concept, we circumvent several pitfalls concerning referential integrity and additionally gain the foundation for a gap-less time travel feature.”

This seems like good training.

“Week 3: The content of week 3 focuses on more advanced structures and operations within the database. The differential buffer, a means to prevent frequent resorting of the dictionaries and rewriting of the attribute vectors, is explained in further detail. Subsequently, also the merge process, which incorporates the changes from the differential buffer into the main store, is illustrated. The retrieval of information via the select statement, as well as related concepts like tuple reconstruction, early and late materialization, or a closer examination of the achieved scan speed, are also part of this week’s schedule. The description of the join operation, which is used to connect information from different tables, concludes this week.”

I have no comment on this section.

“Week 4: Week 4 is all about aggregation. Aggregations are the centerpiece of every business analytics application. Given that huge impact of aggregates on all parts of a business, it is of great importance to understand what aggregate functions are, why we remove all materialized aggregates and go for aggregation on the fly. You will further learn how to greatly reduce the costs of this on demand approach by using the aggregate cache and understand its connection to the differential buffer and the merge process. In the units concluding this week, you will see new prototype applications using the aggregate cache to deliver complex simulations in real time.”

With another week spent on aggregates, without any debate as to whether aggregate removal is a value-add, or worth the effort, this seems like a waste of time. Week 4 could be better spent on hiring a psychologist to analyze why Hasso Plattner is so obsessed with aggregate removal (or should we say reduction, as HANA does have aggregates, but does not call them aggregates).

Hasso Plattner either needs to come in to and speak to our Brightwork psychiatrist to get to the bottom of his aggregate obsession or he needs to admit the only reason he keeps talking about aggregates is that it is a gimmick to try to confuse and sell to customers who lack an understanding of databases.

“Week 5: Week 5 sheds light on some more inner mechanisms of the database. What happens in emergency situations, when for example the power is turned off? Logging and recovery are vital parts to know in order to understand why an in-memory database is as secure as a traditional disk based one. Further, the benefits of replicas are explained. We conclude the week with an outlook onto the implications that arise with the tremendously increased speed at hands.”

SAP promotes its HANA database which is not “in memory” but has more of the database’s tables loaded into memory. Therefore, SAP promoting the idea that a database with more tables loaded into memory is as secure as a traditional one is a marketing point. Therefore can anything that SAP says in this area be trusted?

HANA is far less stable than competing databases, although this is for different reasons. Are the reasons for HANA’s relative instability going to be explained in this course? Probably not.

“Week 6: Week 6 is centered on applications. The last conceptual unit is about data separation into active and passive. After that, we showcase several prototypes and sketch out potential fields to apply the technology, thereby also leaving the domain of pure enterprise solutions, by using main memory databases in weather simulations and medicine.”

Nothing objectionable there.


The purpose of the Hasso Plattner Institute is to educate and advocate as to why everyone should buy HANA. Its courses are to create devotes to SAP’s particular approach to databases. However, there is a problem. HANA is not what Hasso Plattner or SAP says that it is. SAP has presented no evidence that HANA can outperform competing databases. This means that for people taking this course, they are taking it from an institution that was started by a man who has made exaggerated and unsubstantiated claims about HANA.

  • HANA can’t meet the claims made for it by SAP. Will the course talk about that?
  • We receive emails from around the world which show SAP consulting companies providing false information about HANA to customers. Will the course cover that?
  • SAP has made so many false claims about databases that they have undermined rather than enhanced the understanding of databases generally.

So the question is why should the Hasso Plattner Institute be considered anything more than a propaganda apparatus for SAP?

SAP should spend more time trying to get HANA to meet its exaggerated claims versus trying to institutionalize or create a completely biased “HANA university” where receiving certifications or PhDs means agreeing with Hasso Plattner. It has been over six years since HANA was introduced, and the only thing HANA does well is speed data warehousing query performance, but only over previous versions of competitor’s databases.

Search Our Other Hasso Plattner 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.