Comprehensive software reviews to make better IT decisions
SAP S/4HANA and HANA Licensing Series – Part II: HANA DB Hype?
HANA is SAP’s first serious entry into the database market segment. HANA is touted as being superior in performance when working with SAP applications vs. alternate database solutions, but objective benchmarks are lacking. Additionally, the adoption of S/4HANA necessitates adoption of the HANA DB as it is the only certified solution for S/4HANA ERP.
It didn’t take a lot of digging, even for a non-technical analyst in the Vendor Practice such as myself, to uncover significant performance characteristics between a columnar database and a row-oriented database. HANA is a columnar database. In short, columnar databases generally provide performance gains when used for analytics based processing tasks such as those conducted in a data warehouse environment. Whereas row-oriented databases will perform at a higher level when used for the processing of transactional data.
Since ERP systems are first and foremost transactional systems, it would be reasonable to question SAP’s claims that HANA will outperform competitor database products. In these cases, an objective set of benchmarks should set the record straight in quick order. And this is where the problem lies as there simply seems to be a dearth of third-party data comparing HANA database performance vs. the likes of Oracle’s 12c or Microsoft’s SQL Server Enterprise offerings.
SAP’s current lack of transparency into transactional system benchmarking has me looking deeper into how they do benchmark HANA. Of initial interest is that the only benchmark for HANA published by SAP is the BWAML (previously BW-EML) which are related to the BW application. Fitting that the benchmark published matches the strengths of a columnar database, especially in light of the fact that no benchmarks are published for any of the applications running on databases:
It’s easy to see that for SD – Sales and Distribution modules, benchmarks are available on all manner of databases, all except HANA.
Let’s briefly cover some other key deficiencies in SAP’s HANA database benchmarking methodology:
- Where are the benchmarks outside of BW? SAP’s ecosystem of consulting partners is legendary in size and scale; they essentially operate as an extension of SAP and frequently recommend SAP solutions to their client. This clearly allows SAP to exert significant control on the types of information, benchmark and otherwise, that may reflect poorly on SAP.
- Benchmark objectivity is non-existent when judging yourself. In SAP’s own words:
"SAP Standard Application Benchmarks help customers and partners find the appropriate hardware configuration for their IT solutions. Working in concert, SAP and our hardware partners developed SAP Standard Application Benchmarks to test the hardware and database performance of SAP applications and components."
It should be a foregone conclusion that without third-party benchmarks provided by SAP or encouraged by SAP, SAP’s results should be taken with a grain of salt.
- BWAML benchmark is based on outdated Info-Cubes. Presumably with a columnar database the need for BW Info-Cubes is eliminated. Why then would SAP run a HANA DB benchmark predicated on Info-Cubes, which are a set of devices purpose built to perform best upon a row-oriented DB? Most organizations have a lot of overhead and refinement built into their Info-Cubes and may not be ready to throw all that work aside quite yet.
Remember, SAP has a hard “no discount” policy on its HANA database product licenses, making this one expensive line item. It is no secret that SAP and all other enterprise software vendors are publishing benchmarks for the sole reason to promote and increase sales of their products.
As such, it is critical to look beneath the surface of all the glamorous and successful benchmark results to see what was not measured and ask why. The lack of independent or third-party benchmarks should be another red flag that sews legitimate doubt and compels further scrutiny by the customer. Buyer beware! IT buyers should think twice prior to taking SAP’s or its consulting partners’ word for HANA DB performance. Request the benchmarks comparing HANA with other vendor database solutions running on the same application with like parameters. If you can’t obtain this data, proceed at your own risk.
Want to Know More?
Is it true that everything that can go wrong will go wrong? Don’t bet on it to not.
While Microsoft is not a prominent player in the RPA space now with its Power Automate solution, compared to Blue Prism, UiPath, and Automate Anywhere, its latest acquisition of Softomotive, maker of WinAutomation, demonstrates Microsoft’s dedication to mature and expand its RPA offerings.
Test data management tools offer you the ability to provision, mask, and govern the access and use of your test data, alleviating these manual, laborious and error-prone tasks from your testing, operations, and DBA teams.
When trying to implement Agile as a defined process, Scrum turned BAs or other roles into order takers with the title “product owner.” This undermines the entire value proposition of product management.
Agile systems delivery (implemented through Scrum) is quickly becoming an accepted norm in IT. But using Scrum successfully in an organization requires a deep understanding of how it works and why. For example, many of our members don’t understand the importance of selecting a Product Owner who has three ears.
Reeling from the pandemic response executed by governments all the over world, companies are accelerating their implementation of low-cost automation. That bodes well for UiPath – a leader in RPA aiming to go public this year.
Thor, the Norse God of Thunder, tells Jane Foster, the woman he’s trying to impress, that on his home world of Asgard, the realm eternal, science and magic are two sides of the same coin. Had Jane been a part of the operations teams at Google (or other mature online service providers), she would have immediately realized we have a similar technology right here on good old Earth. We call the science site reliability engineering (SRE), and service level objectives (SLO) is the magic behind it. SRE is a powerful concept for organizations that are serious about keeping their customers happy. It is therefore important for them to develop well-thought-out SLOs and make certain that management is intellectually equipped to derive valuable business perspectives from them.
Hell hath no fury like a customer not being able to access an online service when they want to. They expect the online services to always be on, always be accessible, and always treat them like there’s no one else in the world who matters more. Thank heavens then for giving these online services the ability to use site reliability engineering (SRE) to keep their customers happy, engaged, and most importantly, feeling valued.
Info-Tech members moving to Agile are frequently unsure of the role of PMs and the PMO in an Agile environment. Any organization used to traditional (Waterfall) project management will need to make adjustments in support of Agile or risk losing the benefits.