SAP HANA is built on the top of Sybase IQ and it is a multi-million dollar in-memory database solution that is driven by Business Objects Engine. SAP HANA must not be installed in if the company doesn’t own a BO engine because it involves a lot of re-engineering of the reporting architecture. The “views” are BO driven as they are created on top of the data in HANA and that is why in-house BO developers must be present in the company. Any SAP HANA tutorial will display the job description of these BO developers which includes defining the views, creating the universe and start with the reporting aspect of the business. However, SAP HANA uses RAM memory which computes much faster than the conventional UI technologies such as Web Dynpro.
Oracle 12c In Memory database customizes a cache of memory which falls under the umbrella of an existing Oracle 12c buffer pool area. This area is used for the storage of duplicate copies of targeted database objects. The data is stored in a columnar fashion for fast access.
The difference between the two
Here is a list of business requirements and needs which are fulfilled differently by both Oracle and SAP HANA.
- Transparency of the database with existing business applications, Business Integration, and reporting tools
Oracle- It is fully compatible with Independent Software Vendors (ISV) and all Oracle applications along with applications that have been custom-written.
SAP HANA- It is far less compatible, as it requires the recoding of existing applications or new applications to commence work.
- Compatibility with cloud computing, big data, and data warehousing
Oracle- It utilizes dynamic random-access memory, flash, disk memory with full transparency. It has no database size limitations and no futile expenditure on storage facilities because the users don’t have to export their data to the expensive DRAM.
SAP HANA- The DRAM stores the entire database which makes it very expensive. Data warehouses and big data does not fit in the DRAM. Consolidating the database with the cloud is also not a feasible option for big datasets. It has been observed that Hadoop and Sybase can be used for data storage which can be migrated to SAP HANA while running the applications but that is considered as slow.
- Ensuring data availability and security
Oracle- Oracle Maximum Availability Architecture has been inherited by Oracle Database In-Memory that can help in mitigating planned and unplanned outages. This coupled with memory duplication helps in the prevention of node failure.
SAP HANA- The immature product development makes downtime inevitable, and slow recovery from node failure. Since many features are still unavailable, it will be a long time before all real-time high-security scenarios are encompassed in the software.
- Leverages IT talent present in DBA and developers
Oracle- Minimum DBA commands are required, and no new APIs exist, which make Oracle In Memory Database trivial to develop and maintain.
SAP HANA- Retraining of teams or new teams are required, which can grasp and adapt the unique operational procedures and programming practices of SAP HANA.