Skip to Content

Time to update your SAP HANA™ vocabulary

If you recently looked at SAP In-memory Computing webpage, you might had noticed one change. HANA does not stand for “High-performance ANalytic Appliance” anymore. This short blog aims to update you on some new names in SAP In-memory Technology area.

Saplingualogists will be happy – they can write new page in the thick volume of SAP marketing name changes.

“SAP High-Performance Analytic Appliance (SAP HANA)”
is now “SAP In-Memory Appliance (SAP HANA™)”

I think this change makes lots of sense. SAP HANA™ is not meant to be only “analytic” anymore, so my speculations about next versions of HANA turning into HOPA (point #4) are going away. Now it is In-memory Appliance, so the name reflects:

  • Technology instead of the goal,
  • The fact that it is still an appliance in a sense of predefined and certified hardware configurations running the set of pre-integrated software components.

“SAP In-Memory Computing Engine”
is now “SAP In-Memory Database”

Here I have mixed feelings. Not because I got used to “IMCE” (or “ICE” before that) or because “IMDb” is the Internet Movie Database, where you can search for Chuck Norris moviews. 😉

On one hand the “engine” in the previous product name reflected better that it was more than just a database: one of the engine components allows in-database calculations without moving data into the application layer, and includes BFL – business functions library that can be called by other applications and executed “close to the data”.

On the other hand almost every single time I had to explain that computing engine in SAP HANA is SQL-compliant database. New name makes it simpler, but as mentioned in previous paragraph causes the lost of that “extra” delivered with it.

Business Applications based on SAP In-memory Technology

Two weeks ago during Run Better Tour (#SAPRBT) SAP announced the series of applications to be released (called confusingly the “applications roadmap”) on top of the in-memory technology. Dealing with official dozen-words names you will recognize those by additional “Advanced by SAP In-Memory Computing” product name postfix.

Is SAP HANA™ still Chuck Norris of the Enterprise Software?

And at the end – on the fun side. Does it mean that I should change “Chuck Norris” nickname for SAP HANA as well? I leave it up to you. That’s what blog comments area is for 😉

-Vitaliy, aka @Sygyzmundovych

You must be Logged on to comment or reply to a post.
  • It’s tough to keep up with SAP name changes, much less with even faster HANA name changes! Thanks for the recap.

    I think your Chuck Norris meme continues to be helpful. It reminds us that HANA is not actually capable of everything it is rumored to be capable of. Just as Chuck Norris is not actually ….

    … sorry, just had a bearded, very angry visitor. What I MEANT to say is that Chuck Norris actually IS capable of everything, including those things he is rumored to be capable of.

    • Thanks, Vital-E (my new West Coast rap-based nickname for you).

      Great recap, not only of the name changes but of the strategy shift. Can’t wait for the marketing people to change it again to “SAP Memory-based Database (formerly …)” and then to “SAP Database (formerly … (formerly …))” and finally “SAP Skynet(formerly … formerly …(formerly …)))” before it becomes self-aware. (I think Dagfin Parnas made that joke on Twitter last week but I can’t find the link.)

  • Can’t the names ever stay the same?  Sometimes I wonder.

    Yes, I can see the reason behind the name changes.   Someday I will get to play with HANA, and maybe all of this will make a lot more sense to me.  In the meantime, it is interesting reading.


  • Thanks for the blog! We can see that this In-Memory Database is really genuine SAP software. It is not yet publicly available, but the name confusion is already there. To make things even worse, once you have a look at such an NewDB/IMCE/HANA 1.00
    database, you see the prefix HDB all over. Now what
    is that? HassoDB??? Help!!! I am confused.

    I hope at least the version numbers will remain reasonable and self explaining.