Skip to Content
Author's profile photo Witalij Rudnicki

Important Questions (with Answers) about SAP’s in-memory High-performance Analytic Appliance – HANA

I have just returned home after 2 conferences: SAP’s TechEd first in Las Vegas followed by WIS’s Reporting*Planning*Analysis in Orlando. It was a two-weeks speaker marathon for me: 5 lectures, 5 expert sessions, countless discussions over the meal/drink or simply at the corridor, but overall rewarding and enjoyable experience.

One of the hottest topics at the conferences was around SAP in-memory direction in general and about High-performance Analytic Appliance (HANA) in particular. As usually with every new technology, there is lots of noise coming from:

  • Sales and marketing teams making bold statements without sometimes understanding the topic in details
  • Analysts writing stories based on personal sentiment (positive or negative) for the company, product or trend
  • Crowd (including me 😉 seeing the new path to get-rich-quickly and therefore trying to make the evidence of their presence before having something worth to say
  • Broken Telephone” effect

There is and there will be a lot of noise, so you need to filter what’s facade and what’s reality. The first wave of noise – after SAPPHIRE’10 – came and went quickly. It left behind new SCN forum “SAP HANA and In-Memory Computing Business Data ManagementSAP HANA and In-Memory Computing“, which dried up very quickly. Well, there was not much to discuss at that time. But now second wave is coming – SAP HANA is becoming a reality and is causing activation in the eco-system, including me.

During last two weeks I saw the full spectrum of feelings caused by the topic: from baseless hyperoptimism to arrogant ignorance to cynic skepticism. The same was with the spectrum of questions triggered: from relevance of persistency mechanisms for in-memory databases to the future of SAP NetWeaver BW. I think proper discussion should start from the basis. Below is my attempt to address the most important (IMHO) questions.

1/ What is SAP HANA and, more importantly, what is SAP ICE?

There is great thing SAP introduced with this latest technology: separation of the stack name – HANA – from the name of the engine – ICE – the core software component. Let us first look into the history though.

BW Accelerator (BWA)” name was used for both – software as well as complete stack of software+hardware. This was a source of multiple misunderstandings and misinterpretations.

It was even more confusing with “SAP BusinessObjects Explorer, accelerated (BOEA)“, because now, although named after the front-end tool, the appliance still had BWA in the heart, even though the deployment scenario without SAP/BW became available. This caused pop-up’s of different names in different SAP materials, but I do not think there was any consistency in using them: “BO Accelerator”, “BI Accelerator” (yeah, welcome back, BIA :-), “Open Accelerator” etc.

Now SAP is introducing the new stack with the new software component in the heart, called “SAP In-memory Computing Engine (ICE)“. ICE is the in-memory platform consisting of database and calculation engines, and has been referenced in the past as “NewDB”, “HassoDB” or “BAE – Business Analytic Engine”. It is SQL ANSI 92 compliant in-memory database with full ACID transactions support, capable of storing tables in both column-oriented as well as traditional row-oriented form. Part of the SAP ICE is the calculation engine, which allows in-database calculations without moving data into the application layer.

In turn “High-performance ANalytic Appliance (HANA)” is the complete stack of SAP-certified hardware configurations with pre-installed ICE and some other software components. E.g. SAP HANA 1.0 will have Sybase Replication Server pre-installed.

2/ SAP HANA 1.0

The first release of the new in-memory analytics appliance from SAP is targeted for side-by-side deployments along SAP Business Suite applications. Please have a look at the top row on the picture in “The BW – HANA Relationship” post by Thomas Zurek. Sybase Replication Server – pre-installed in HANA 1.0 – will allow almost real-time replication of data from SAP ERP or CRM into ICE for further analysis. This real-time data from operational system can be mashed up in HANA with data from BW or some other 3rd party applications. For the latter data is not replicated, but loaded into ICE using SAP BusinessObjects DataServices.

Although I have not seen official dates for HANA 1.0 published, let me repeat what has been announced by SAP during multiple presentations. Ramp-up starts on November 30th of 2010 and go into General Availability when success KPIs for HANA 1.0 product are met (probably around late spring 2011).

3/ Business case for SAP HANA 1.0

SAP HANA 1.0 is intended for analytics solutions that require:

  • real time data,
  • high performance in-memory based processing,
  • agile data modeling.

We need to understand that SAP HANA itself is like an empty database, and analytic solutions on top of it have to be:

Obviously new technologies are opening new possibilities. Marge Breya, EVP and GM, Intelligence Platform and SAP NetWeaver Group, during her meeting with SAP Mentor Initiative at TechEd pointed out that HANA enables not only powerful analytics, but as well “algorithmic processing” like automated management of exceptions in streaming data.

4/ Beyond 1.0: HANA or … HOPA?

Although it is only version 1.0 of SAP HANA that is going to become available soon, most of the eyes are already looking into the future for the “on-top” deployment options – SAP’s in-memory as a replacement of traditional databases for ERP and BW – presented on the bottom row of the picture in Thomas’s blog. Although we saw a demo of ERP system running on in-memory during TechEd in Las Vegas, I will save my and your time i/o speculating on this topic right now. Hopefully we will return to it in future blogs.

I found that SAP does not always clearly communicate the difference in versions and their availability of new in-memory products, so some people expect they could run their BW or CRM on top of HANA “tomorrow”. Well, you need to be a bit more patient.

The only question I would have right now, is once we see the option of running ERP on top of in-memory database 2.0 coming, will it still be called HANA? I would expect rather something like “High-performance OPerations Appliance” or HOPA 🙂 Or may be simply ICE, because we would not need all the other surrounding software like Sybase Replication or SBO DataServices in the stack?

* * *

This blog is becoming too long, so let me save the question about how HANA/ICE are related to other SAP in-memory products for HANA 1.0 vs other SAP in-memory products.

-Vitaliy, aka @Sygyzmundovych

PS. Nov 6th 2010: We are living in the fast pace world indeed. I had to correct this blog the very next day after it has been published due to some important changes in HANA 1.0 architecture. And then few days later some other mention in the blog (not related to HANA directly) became the history as well. Viva La Evolucion! 🙂

Assigned Tags

      You must be Logged on to comment or reply to a post.
      Author's profile photo Ethan Jewett
      Ethan Jewett
      Thanks especially for making the distinction between the stack and the individual software components. That is a really helpful way to think about this.

      I'm curious where the ICE name comes from. Is that name currently internal to SAP, or is it the public name of the product?

      Author's profile photo Witalij Rudnicki
      Witalij Rudnicki
      Blog Post Author
      Ethan, most of SAP technical folks are still using NewDB in the discussion, but accordingly to SAP marketing the official name is "In-memory computing engine" i.e. ICE.
      Author's profile photo Former Member
      Former Member
      This blog clears up some of my questions.  Of course it leads me to more.  But I'll keep my eyes open for more information / blogs about HANA.

      ICE - Interface, Converstions, Ehancements

      Another acronym. 

      Thank you for the explanation!


      Author's profile photo Witalij Rudnicki
      Witalij Rudnicki
      Blog Post Author
      Hi Michelle. There are 390 meanings of ICE acronym, accordingly to 🙂
      Author's profile photo Former Member
      Former Member

      I love it.  I have a new favorite site.

      Thank you!

      Author's profile photo Tammy Powlas
      Tammy Powlas
      Thank you for taking the time to do this.  I was so busy with hands-on sessions that I didn't get any HANA time. 

      I like your HOPA acronym.

      Excellent blog, as always 🙂

      Author's profile photo Witalij Rudnicki
      Witalij Rudnicki
      Blog Post Author
      Thanks, Tammy. May be I should go to work for marketing department inventing acronyms for existing and non-existing products? 😉
      It was nice meeting you during TechEd, unfortunately from my side - I didn't join Mentors during any hands-on :-/
      Author's profile photo Former Member
      Former Member

      nice plug for HP and i only wish somebody from IBM had something similar to say. any idea who would do the In-memory coding?


      Author's profile photo Witalij Rudnicki
      Witalij Rudnicki
      Blog Post Author
      Greg, not only HP and IBM are in the game, but Fujitsu and Cisco as well. It makes it fun.
      What do you mean by doing "In-memory coding"? If it is about the ICE as a product - it is SAP developers. If you mean building applications on top of ICE in 1.0 - it will require a set of skills, probably separated between couple of people - SQL developers, BO Universe designers, BI authors. Pozdrawiam. -Vitaliy
      Author's profile photo Martin Lauer
      Martin Lauer
      hi greg,

      IBM recently acquired Netezza:
      which sell appliances for data warehouses

      and there's some software. e.g. Cognos TM1:

      Can you recognize a pattern?
      kr, martin

      Author's profile photo Davide Cavallari
      Davide Cavallari
      Hi Vitaliy,

      great job, you wrote a very clear piece, thank you.

      I was wandering whether BW would still be really needed in an on-top scenario.

      Perhaps, modelling of data could be done directly in HANA appliance, making BW's modelling framework unnecessary.

      Please let us know what do you make of this, and thanks again for all your informative blogs.


      Author's profile photo Former Member
      Former Member
      Hi Davide,
      Please take a look at this blog about HANA/BW discussion >
      The BW - HANA Relationship


      Author's profile photo Alexander Schuchman
      Alexander Schuchman
      If I ignore all the marketing hype, it's really exciting to see a database finally perform at the same level that users have been asking for since IT started delivering tools.  The combination of best of breed front-end BOBJ tools with a super charged database is my favorite part...not to mention all from one software vendor.

      I'm really looking forward to how this database changes our BI ecosystem! 

      Author's profile photo Former Member
      Former Member
      Thanks for such an informative article Vitaliy. Looking forward to your blogs on this topic.


      Author's profile photo Former Member
      Former Member
      As usual, a very much "wanted" blog by Vitaliy which clarified the HANA concept. I just need more clarification on your 3rd section "Business case for SAP HANA 1.0": what do you mean by "Agile Data Modeling"? does this mean that changes in OLTP structures are easily reflected in BI/DW structures in HANA??

      Thank you so much for sharing your thoughts Vitaliy,

      -Ali Q.

      Author's profile photo Witalij Rudnicki
      Witalij Rudnicki
      Blog Post Author
      Thank you for nice words, Ali.
      "Agile Data Modeling" with HANA is an idea of giving business users capability of building their own analytic models independently of IT. New modeling tool will be available for that. I am trying to write about facts, and not rummors, so corresponding blog will wait till later times. But because I am still human, and speculation is in my veins as well 🙂 I think it will be something along this line
      Author's profile photo Former Member
      Former Member
      Whatever happens after HANA 1.0 one thing is sure. The name will change. It was fun to see the BO colleagues at TechEd trying to remember all the new names.

      I'm really looking forward to HANA/HOPA/etc. being able to support BI-IP.

      Author's profile photo Witalij Rudnicki
      Witalij Rudnicki
      Blog Post Author
      Hi Dirk. It has to change. I must say it is really a mess what I see is happening, and it surprises me that marketing still hasn't learned from the past. It is not only that HANA name does not fit into the future scenarios, like being the db for Business Suite applications. But it is as well about the fact that One Voice has not provided official acronyms e.g. for In-memory computing engine. But people cannot pronounce long words and acronyms are part of our live. So, I see SAP sales using "ICE", and SAP technical people using "IMCE". Another example: "ODBC driver for HANA 1.0", but HANA is not a software, it is an appliance. ODBC driver should be for "ICE".
      Naming evolution will be part of the journey 🙂
      Author's profile photo VINCENT LEFEBVRE
      High Vitaly,

      Thanks for this very interesting blog.

      ICE make me think at Inter City Express, the german high speed train 🙂

      Author's profile photo Former Member
      Former Member


      Thank you very much for this detailed explanation 🙂