re: SAP: We'll Be No. 2 Database Player By 2015
I hear you... there are definitely scenarios where extremely fast read/writes will be beneficial, but they are pretty rare. For the average SAP user, that is running say AR, AP, GL, PP, MM, HR, SCM, what does improving the response time from 2 seconds to .2 seconds do for them?... not much. SAP tends to be back-office applications where response time is not that critical, not front-office applications like store fronts.... It would definitely be cool from a technology perspective, but I don't understand the ROI.
This will also introduce a whole new layer of complexity unless you want to make HANA your master database to replace Oracle/DB2 for every application, not just ERP.... If you use HANA for SAP, you will need some sort of costly MDM solution to aggregate and synchronize all of the tables for other applications that use, for instance, your master customer tables.... I think in-memory, for the vast majority of users, is still a solution in search of a problem. Particularly when you are talking about using in-memory for OLTP (several TBs of data) as opposed to say OLAP (several GB of data). I wish SAP would have just stuck with DB2 as their preferred DB and Oracle if users want it. This is going to get messy.