- Hasso Plattner and SAP made a number of statements around the necessity of removing aggregates.
- In this article, we debate this claim.
We debated the benefits of HANA aggregates with Vinnie Mirchandani.
“It is fundamentally different. It streamlines your data architecture by not storing aggregate balances but calculating them as needed. It is memory hungry. However, it is another way to run enterprise apps. Same with Third Party Maintenance. Given the stubborn economics of IBM and Oracle in particular and the cost of DBAs etc, at least some companies are willing to consider them. My point is after 50 years we should be encouraging more companies to target the relational cost base. Oracle is trying to reduce the labor component with its autonomous features but wants to layer on its IaaS on top, not really improving the economics.”
Our Response on Aggregates
SAP’s arguments around aggregates are entirely fallacious. We covered this in the following article. What is the Actual HANA Performance?
Let us ask the question of why SAP proposes removing aggregates. One reason is for compression. However, compression is only relevant because HANA is priced per GB. The size of the database does not matter very much. John Appleby back when he was the number one shill for HANA made the rather ludicrous statement that hard drives “take up space.” (we covered this ridiculous comment in the article How Accurate Was John Appleby on Moving BW to HANA.
I don’t have to tell you, that makes no sense. But SAP was doing anything they could to try to push the idea of reducing compression. Literally, no one outside of SAP or SAP mind controlled resources thinks who are riding the SAP money train that aggregates are a problem. There is simply no technical argument against them.
Literally no one outside of SAP or SAP mind controlled resources thinks who are riding the SAP money train that aggregates are a problem. There is simply no technical argument against them.
A second reason for emphasizing aggregates was to fake innovation. Our research shows that HANA is a type of fake innovation as we covered in How to Understand HANA as Fake Innovation.
Outside of removing aggregates and indexes, we can identify no other “new” items introduced by SAP. But the problem is that both of these ideas are pointless and would have only been proposed by a database novice. But remember, no one at SAP can tell Hasso he is unqualified to make such statements. And this is a primary problem with HANA. As I pointed out, HANA cannot meet its design objectives, because they were not realistic, to begin with. It was like Theranos, Elizabeth Holmes had no idea how to accomplish her objectives with the blood testing machine — she only had a hypothesis. And a hypothesis that ended up being false.
Elimination of aggregates is “not a thing.” Hasso had to say this was his contribution because he faked the origin of HANA as we covered in the article Did Hasso Plattner and His Ph.D. Students Invent HANA? Hasso does lacks the background to design a databases. So don’t take your information from him.
Your last point moves on to reducing the labor component of databases. Sure, that is fine, but again, that is not the primary focus of the beginning of your comment. I don’t want to address five different topics at once and do none of them proper service. This is exactly how Hasso tricks people, he keeps switching topics so nothing can be validated. If you feel confident on the topic of aggregates lets stick on that topic before saying that the real point is some other topic. Secondly, HANA is the most expensive database of any of the databases in TCO. So it is difficult to see where the economics argument holds water.
What you just wrote about aggregates is not correct, and it is boilerplate SAP marketing flim flam. This argument has already been broken into pieces.”
The Purposes of Aggregates in SAP
Aggregates had an additional purpose in SAP, which is explained by Rolf Paulson.
“Performance is one reason for the need of aggregates, but this is only needed for large tables. Many aggregates in SAP ERP exists because you simply cannot define aggregate views like SELECT SUM(…) FROM sales order GROUP BY department. Even if you have a table with let’s say several 1000 rows that any database just can aggregate on the fly and you want to show aggregates in a data grid, you must aggregate these data first with a stupid loop in ABAP. Just as recently as there are CDS views this is not necessary anymore.”
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 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