Recently, SAP announced a definitive agreement to acquire Sybase for $5.8 billion, at $65 a share, a 44% premium over the share's three-month average price. The transaction is expected to close during the third quarter of 2010. Sybase will operate as a standalone unit under the name “Sybase, a SAP Company,” and be run by Sybase’s management team.
Although execs from SAP and Sybase have stressed mobility, real-time information, in-memory, and analytics benefits that come from this acquisition, the increasing pressure from Oracle cannot be undermined. Oracle’s stronger focus of stack level integration and selling around applications, middleware and database, and recent acquisition of SUN has put pressure on SAP.
SAP-Sybase Deal Offers A Lot Of Synergies
SAP and Sybase offer many benefits ranging from in-memory technologies, databases, analytics, and data integration to mobility and ILM.
Finally, SAP Is Acquiring (At Least A Mobile) Middleware
SAP’s customers and the analyst community have been speculating about the possibility of SAP acquiring a middleware company for a while. After it had missed out on acquiring one of the heavyweights like BEA and hesitated over TIBCO and Progress Software, SAP and Sybase agreed yesterday on the $5.8 billion transaction.
Sybase used to be a database, but its database’s visibility in the market decreased so dramatically that, in a recent Forrester survey, it wasn’t considered to be a primary database choice by any application domain. A good share of the 4% of open source databases used in the ERP space are actually SAP’s open source MaxDB (based on SOFTWARE AG’s original ADABAS D), which is a default for SAP systems if a customer doesn’t provide a third-party database like Oracle or DB2. SAP is unlikely to replace this default database with Sybase. This would be an even less important database than MaxDB, which integrates well with NetWeaver. But different analysts have different opinion and you might like to look for Boris Evelson's take on the impact of Sybase's database. If SAP runs a careful post-merger process, it will recognize Sybase’s database knowledge and employ all the engineers who have already developed in-memory database capabilities to bring Hasso’s idea from the Palo Alto “garage” to full product availability. While SAP has deployed in-memory capabilities in its analytics technology stack, the in-memory capabilities for transactions are still in the lab.