Brief introduction
SAP claims that Hana is the fastest database, so SAP's new ERP system S4 no longer supports Oracle
A new feature of Oracle 12c is the ability to convert between rows and columns for the same table
SAP wants users to think of Hana as a unique technology, but in this article you can see that both memory and Columnstore are not proprietary technologies of SAP
Hardware speed and database design confusion
Hana mixes two different concepts together:
1. At the hardware level, Hana needs to load the data into memory
2. At the database design level, Hana is a column-based database
This confusion in fact in SAP ERP has been used, and the use of success, SAP believes that SAP's own ERP can better integrate the application, the risk of integration less.
The integration of SAP ERP is at the level of application, and Hana is at the vertical level until the database layer
One reason why SAP wants users to migrate to Hana is that SAP has decentralized the application logic to the database, unlike previously storing the database as a data store.
PS. But I think these interfaces are open to other databases.
A real opportunity for Hana
The real opportunity for Hana was to put ERP and other SAP applications on Hana, and then the analysis engine could run on the same hardware, and integration and transformation were no longer needed.
But what about non-SAP applications that can't run on Hana and they don't need integration?
In addition, Hana is very expensive, and currently Hana supports a small subset of SAP applications
The fastest database in the West?
Look at the headline, the writer's kinda funny.
Hana is obviously not the speed champion, as SAP says. One important reason or weakness is that Hana is a column-based database, which is an incorrect design for a non-analytic database. Although SAP claims to be, it is not from a computer science point of view. (SAP has a paper that specifically describes the performance of a column database.)
For the insertion, deletion, and update of the trading system, the column database is slower than the row-type database
The debate about speed
Oracle's John Soat's article on Forbes has countered the speed of Hana, and it's important to note that Hana has not released performance metrics for transaction processing. Maybe it's done, but it's not good enough.
Oracle 12c Data Dual mode
An important advantage is that Oracle 12c can present data in memory in both row and column. In addition to pure analytical operations, Oracle's flexible design has the performance to triumph over Hana.
SAP believes Oracle's memory technology is immature, while Hana has 7,000 users, but most of the users don't really use Hana.
Conclusion
The advent of Oracle 12c in-memory columnstore makes it no longer sufficient for SAP to migrate users to Hana.
SAP as a manufacturer of applications, now the data layer to the user, the results, only to wait and see.
The following paragraph is actually what I admire most:
At the Computer History Museum in Mountain View, there was an exhibition that once software was tied to hardware, software was not an industry at the time, and IBM released programs that ran only on IBM hardware. Software not only charges, at the software level there is no competition.
What we now know about the software industry is actually after the decoupling of hardware and software, the US enforcing anti-trust legislation for proprietary software and hardware vendors. Hana, as an application and database coupling, is controlled by a single vendor, which brings us back to the earliest days of software.
PS. Oracle's Exadata is also a combination of software and hardware, but Oracle does not require that the database be run on Exadata
The conclusion is:
* The future is not the same as a column-only database.
* Only SAP can develop a high-performance database like Hana is also wrong
Which one is faster for HANA and Oracle 12c