When Vishal Sikka, SAP Executive Board Member, Technology and Innovation, announced SAP In-memory Appliance software, at SAP TechEd last year – when it was still simply called SAP HANA – only a few people could imagine what that would mean for SAP. By the time Hasso Plattner gave his keynote speech at SAPPHIRE NOW in Orlando, however, it was clear just how big of an the impact SAP HANA would have on the complete SAP portfolio.
SAP HANA was developed at the Hasso Plattner Institute in Potsdam, Germany. The software, combined with the necessary hardware, or servers, uses the principle of in-memory technology, in which data is stored in the main memory rather than in disk or database. With SAP HANA therefore, data can be accessed much more quickly than before, enabling data analysis in seconds – basically in real time.
On the first day of TechEd Madrid, it was not only the line to check-in at the conference when the doors opened at 8 a.m. which seemed endless. All sessions to do with SAP HANA also drew massive crowds. The lecture on “Roadmap for SAP HANA” was attended by well over 50 people. If you didn’t arrive at least ten minutes in advance, you were guaranteed a spot in the last row, where it was nearly impossible to hear a single word. Those who attended SAPPHIRE NOW in Orlando, however, were in luck because a roadmap for SAP HANA was presented at the event in May. You can read all about SAP’s plans for the the product in “Roadmap: SAP HANA”.
In contrast to some presentations at the last TechEd, this year the speakers were more concrete. Read on the next page:
- Four scenarios: SAP HANA in use
- Five servers: Hardware for SAP HANA
On the first day of SAP TechEd Madrid, we learned about four specific scenarios for implementing SAP HANA:
1. Accelerator scenario – for faster data analysis
In this scenario, HANA is deployed to speed up data analysis. A traditional database based on ABAP is required. Applications such as SAP CRM, SAP ERP or SAP Business Suite access data from that database by way of the SAP Application Server. The SAP HANA database runs in addition to the traditional database, enabling the data to be input and analyzed.
2. SAP HANA as a database in the Application Server
For this scenario, SAP NetWeaver Business Warehouse 7.3 is a must. The tables and data that are to be analyzed by SAP HANA must be manually defined. For large tables, SAP offers a special Data Modeling Service which makes the installation of data easier. Furthermore,in the SAP HANA Studio, administrators can define which tables and data in an application should be synchronized with SAP HANA.
3. Data Mats and SAP HANA
Real-time analytics are especially useful for BI analyses and reporting. SAP HANA can now be deployed with BI software like BusinessObjects 3.0 and 4.0. However, SAP HANA does not work with BusinessObjects Explorer.
4. Applications powered by SAP HANA
While SAP HANA functions as a sort of catalyzer in the other three scenarios, in this scenario SAP applications run completely on SAP HANA. Here, SAP NetWeaver Business Warehouse 7.3 is not required.
At the SAP HANA stand there were five servers on display that can be used with SAP HANA.
- Fujitsu Primery RX 600 S6, Intel E7-4870, 20 cores, 256 GB RA, for small SAP HANA use cases
- Dell Power Edge R 910, Intel E7 480, 32 Cores, 512 GB RAM, for medium SAP HANA use cases
- IBM System 3850 XS, for small and medium SAP HANA use cases
- Cisco, Intel E7 4870, 40 Cores, 512 GB RAM, for medium SAP HANA use cases
- HP Pro Liant DL 580 G7, Intel E7 4870, 40 Cores, 512 GB RAM, for medium SAP HANA use cases
Brush up on more topics related to SAP HANA with these articles:
Interested in more stories from SAPPHIRE NOW and SAP TechEd from Madrid? Also visit the Events Newsroom.