What’s New in SAP HANA Cloud in September 2022
Summer is slowly coming to an end, at least for the colleagues located in the northern hemisphere. And with the end of the summer, we are also approaching yet another end of a quarter. With this blogpost, I want to provide you with a summary of the exciting innovations that have been introduced to SAP HANA Cloud in Q3 2022. In case you want to take a quick glimpse at some of features introduced, take a look at my personal QRC3 2022 highlight via our teaser.
To get a detailed overview of individual functionalities and changes, including demos and a Q&A, don’t miss out and register now for our release webinar hosted by the SAP HANA Cloud product management team.
But for now, let’s look at the main highlights of the recent SAP HANA Cloud release:
SAP HANA Cloud, data lake
Our petabyte scale data lake is an integral part of SAP HANA Cloud. It allows users to store and manage all their data in a single solution. No matter, if you are looking for in-memory storage, disc capacity for warm data, or petabyte scale storage options, SAP HANA Cloud offers all in one box.
Always striving for improvements to our product, there is one especially notable innovation in QRC3 2022 for the SAP HANA Cloud, data lake.
Store relational engine data in SAP HANA Cloud, data lake Files storage
With the QRC3 2022 of SAP HANA Cloud, it is now possible to store SAP HANA Cloud, data lake relational engine data inside of the SAP HANA Cloud, data lake file storage.
This reduces data storage costs significantly. Moreover, scalability and throughput are improved. There is no need to over-provision storage any longer, to improve performance.
Last but not least, compute and storage resources are separated more clearly.
If you are curious to learn more about the change introduced, take a look at Jason Hinsperger‘s blog post.
These newly introduced functionalities offer a higher degree of control when upgrading and provisioning SAP HANA Cloud, SAP HANA database instances. Users are no longer forced to choose the latest version when upgrading or provisioning. This way instances and landscapes can be kept aligned on different QRCs more easily.