back to article Look over here! SAP unveils big data HANA update

Teutonic enterprise resource planning provider SAP has unveiled a cloudy HANA big data update, in an effort to drum up more interest in its in-memory databases. The SAP HANA Vora product will apparently extend in-memory computing to distributed data, and allow companies to mash up their corporate and Hadoop data. HANA Vora …

  1. Anonymous Coward
    Anonymous Coward

    Seems like a rather poor uptake...

    Two thirds of the 120 organizations running SAP have rolled out HANA, or plan to deploy it, according to a survey by the UK and Ireland SAP User Group, which shared its figures with The Register.

    The group said nearly one third of users have rolled out or plan to roll out HANA in the next three years.

    So, if I understand this right, 1/3rd of users have rolled-out or will do so within the next 3 years (para 2); another 1/3rd (para 2 minus para 1) plan to roll out after 3 years; while the remaining 1/3rd have no plans to roll it out at all.

    Not exactly flying off the shelf is it?

  2. IlyaGeller

    SAP uses the obsolete SQL Industry standard.

    For instance, there are two sentences:

    a) ‘Pickwick!’

    b) 'That, with the view just mentioned, this Association has taken into its serious consideration a proposal, emanating from the aforesaid, Samuel Pickwick, Esq., G.C.M.P.C., and three other Pickwickians hereinafter named, for forming a new branch of United Pickwickians, under the title of The Corresponding Society of the Pickwick Club.'

    Evidently, that the ' Pickwick' has different importance into both sentences, in regard to extra information in both. This distinction is reflected as the phrases, which contain 'Pickwick', weights: the first has 1, the second – 0.11; the greater weight signifies stronger emotional ‘acuteness’; where the weight refers to the frequency that a phrase occurs in relation to other phrases.

    SQL cannot produce the above statistics – SQL is obsolete and out of business.

    SAP got the problem.

    1. Stretch

      lol you again. you silly man.

  3. Rob 54

    My two cents

    SAP face many challenges while encouraging uptake... very few companies will jump in as early adopters, the cost was originally prohibitive, renegotiating contracts takes time, existing hosting arrangements wont meet the min specs but are typically long term commitments with datacentres etc.

    My organisation will be replatforming onto HANA as our core DB in 1.5 years.

    The traditional SQL just doesn't cut the mustard anymore, we are pushing the systems well beyond their capabilities and need a better DB to achieve the real time results people expect these days.

    IMHO SAP bashing is easy to do, they are far from a perfect company but do have some solid products, despite some having a track record of borked deployments by partners, but the thousands of successful deployments never make the press.

  4. PlinkerTind

    Two different HANA databases

    There are two different versions of the HANA database everybody talks of; the clustered version that runs on x86 nodes. Maybe all nodes can aggregate 32TB RAM or so, in total. Add in compression and you can handle large databases from RAM, very fast. These RAM databases are (almost) exclusively used for reading, that is, analyzing data just like a data warehouse. Oracle TimesTen is also a RAM database that is only used for reading data, analysis. RAM databases typically have very rudimentary locks, or no locks at all - as they are designed for reading data, not transactions. Scale-out RAM database, read only.

    HANA has also another database, one used for storing data, it is just a traditional vanilla normal database, for transactions. And this scale-up database is not clustered. It is only used on a large scale-up server, such as the SGI UV300H with 16-sockets. It stores all data on disks, not on RAM. Nobody talks about this traditional transaction database for disks.

    So a HANA installation has two databases, one for storing data on disk, and one for caching data in RAM for analysis.

    But, Oracle will release the SPARC M7 server this year. It is a single scale-up server with up to 64TB RAM. And if you apply compression, say 10:1, you can analyse very large databases from RAM. And a single scale-up server with 64TB RAM is faster than a scale-out cluster with 64TB RAM. So why don't people just use a single scale-up server instead of this HANA cluster?

    1. Steve30

      Re: Two different HANA databases

      Do you have a link to describe the traditional HANA vanilla disk base database ?

POST COMMENT House rules

Not a member of The Register? Create a new account here.

  • Enter your comment

  • Add an icon

Anonymous cowards cannot choose their icon

Other stories you might like