SAP HANA architecture
SAP HANA’s in-memory, column-oriented architecture is built for fast queries and high-speed transactions – but it also includes – database management, application development, advanced analytical processing, and flexible data virtualisation.
The history of SAP HANA
In the mid-2000s, co-founder of SAP, Hasso Plattner, was on a mission. He wanted to develop a database that could process transactional and analytical data – and answer any business question – in real time. 2010, SAP HANA was born and now 31,000+ direct customers run on SAP HANA today.
Tips for migrating to SAP HANA
When moving from a traditional database to an in-memory and column-oriented database, there will be new things to address. But many of the steps in implementing SAP HANA are the same as any database implementation.
How you manage with SAP HANA is much different than in legacy databases and most implementations will result in a smaller data footprint. Dedicate time to research the technology, explore success stories, read the blogs, and develop a list of implementation resources.
Legacy systems always have some outdated applications, custom code, and data that must be addressed in the migration planning.
Determine the amount of memory your main data set will require. Plan the memory size for static and dynamic data as well as the disk size requirements for “persistent storage.”
This is a wonderful opportunity to remove bad, duplicate, and old data to streamline your systems and reduce your data footprint.