« In-Memory : is it all about speed? | Main | Learning Basic SQL with SAP HANA »

SAP HANA SPS 09 - Dynamic Tiering - pure In-Memory goes disk based

SAP introduced the SPS 09 Service Pack for SAP HANA; These SPS's (SUPPORT PACK STACK) are more then minor release levels with error fixes but with introduction of new functionality sometimes mighty features - they are similar to the Oracle patch sets and clearly show how vibrant the evolution of SAP HANA really is.

Among a lot of other new features they introduced a feature called SAP HANA Dynamic Tiering. Hm ... to be honest I did not have any idea what it should be about when I heared about it the first time. But ... Hey!!!!
The stuff is about Data Aging, hot and warm data, data which should be in-memory and data which could reside on disk. but now please sit down.

With that feature SAP did not less then integrate a traditional Sybase IQ column store database engine buffer cached into SAP HANA for archival of warm data.

So this is really funny and a tremendous step indeed! because Oracle did it vise versa; Integrating an in-memory column store into it's traditional database engine.

And SAP did a lot of engineering to integrate the second engine so that from outside both engines appear as one. Just an extended table definition is needed - something like another table type  - in SAP HANA  dictionary points to the other database engine and processing.

That is a tremendous step because SAP HANA now is capable to store tons of historic data on disk almost without a limit. Which now adds another feature to compete with Oracle.

Future releases will improve seamless inegration of both engines, also do have one backup tool even to do Crash-recovery.

SAP HANA is on the run to bypass ...

It's simply amazing how SAP HANA develops and the Dynamic Tiering stuff besides other cool features like tenant-databases which Oracle introduced in 12c - positions SAP HANA against Oracle even better and better



References (2)

References allow you to track sources for this article, as well as articles that were written in response to this article.

Reader Comments

There are no comments for this journal entry. To create a new comment, use the form below.

PostPost a New Comment

Enter your information below to add a new comment.

My response is on my own website »
Author Email (optional):
Author URL (optional):
Some HTML allowed: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <code> <em> <i> <strike> <strong>