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.
Most of us have already heard that Sybase will become part of SAP — or, to be more precise, that SAP and Sybase announced that SAP's subsidiary, SAP America, Inc., signed a definitive merger agreement to acquire Sybase. When this acquisition takes place, there will be various impact areas across SAP and Sybase’s combined portfolio. Rather than discussing this big picture, I would like to focus on SAP for Banking.
In this podcast Principal Analyst Boris Evelson discusses SAP's recent announcement on their intention to acquire Sybase. From the business intelligence point of view, Boris breaks down the obvious and not so obvious effects the acquisition will have on SAP's BI and data warehouse capabilities.
SAP today announced an agreement to acquire Sybase, Inc. for $5.8billion. Sybase has a broad portfolio of solutions, so the question comes to mind: what is the strategy, the driving force behind the deal? What are the Sybase crown jewels that SAP is after?
The main three assets Sybase brings to SAP are obviously a database, a mobile infrastructure and real-time analytics. Is it the combination of all of these assets or is there a distinct difference between those portfolio elements? Here are some first thoughts from my side on SAP’s strategic intention for the deal:
This deal is not focused on Sybase’s database assets. Why?
The Sybase market share on databases is too small to make a big difference for SAP. Most SAP applications are currently running on Oracle, and there is little appetite in the market for replacement projects.
SAP is Oracle’s biggest database reseller and makes significant business out of this and won’t shoot itself in the foot. Thus they will of course continue to sell and support Oracle, DB2, etc… Anyways it’s an important element of SAP’s strategy to support multiple databases, but first it means investment to extend this support to the new family member (Sybase’s database is currently not supported!). In the long run, however, it won’t hurt to have in-house database expertise as the market changes and new opportunities will come.
After almost a year of work, Jeffrey Hammond and I finally published the Agile Development Management Tools Forrester Wave™ evaluation. So I thought I would share some of the observations from this report. Agile has changed the way in which development teams work, and this changed motivated the Forrester Wave. A change that has meant not only new ways of working, but also new vendors have entered the traditional application life-cycle management marketplace. The Forrester Wave focused on the following main areas:
Today's announcement that SAP will acquire Sybase is a major event in the software world, but it will not fill key gaps in SAP's integration capability. If the $5.8 billion deal goes through SAP will gain strong mobile integration and database features, but the existing shortcomings of NetWeaver PI in the areas of application and process integration in heterogeneous environments remain.
NetWeaver is a credible solution for integration challenges between numerous SAP business applications, but it has proven to be inadequate for solving integration between SAP apps and apps from other sources (both home grown and other commerically available business applications). The Sybase acquisition does not alter this fact.
For a deeper look into the challenges faced by SAP customers when trying to rely on NetWeaver for their non-SAP integration needs, refer to our May 5th document entitled, "It's Time To Tame The ERP Integration Beast".
SAP gets its own relational (Sybase ASE) and analytical (Sybase IQ) DBMS. Why is this a positive since SAP already has tight partnerships with major DBMS and DW vendors such as Oracle, IBM, Microsoft, Teradata, and HP? Simple. First, SAP can now control the code. Second, SAP can now potentially reduce reliance on DBMS partners, most of whom (Oracle, IBM, Microsoft) have their own full software stacks and therefore compete, often putting a strain on partnership relationships. True, Sybase ASE has a rather low market penetration, other than on Wall St (see Stefan Ried's blog), but since SAP BW takes care of most of the traditional RDBMS design and implementation tasks, Sybase could be positioned as a black box engine under BW, that does not require separate design, administration and maintenance environment. *** Update. SAP just confirmed that each of its applications can run on an independent database, so having mixed DBMS platforms under ERP and BW will not be an issue.
SAP also gets highly relevant (for low latency BI) and currently missing CEP technolgy from the Sybase Aleri acquisition and an OEM version of Coral8.
SAP customers may also benefit from advanced analytics from Fuzzy Logix, integrated and embdded in SybaseIQ
Sybase gets a badly needed BI front end on top of its Sybase IQ analytical DBMS. While Sybase is leading the market in the columnar DBMS, it is somewhat challenged selling and positioning the product with the business buyers, since they can’t really see, feel, or touch it.
When preparing for our upcoming Forrester Data Management Tweet Jam (May 13th, 2-3pm ET) -“What BI is Not!”- we got together with a few of Forrester’s data management and BI analysts to discuss some of today’s key BI questions.
The question on the table was, “How will social media impact traditional BI?”
When preparing for our upcoming Forrester Data Management Tweet Jam (May 13th, 2-3pm ET/8-9pm CET) -“What BI is Not!”- a few of Forrester’s data management and BI analysts got together to discuss some of today’s key BI questions.
One of the questions on the table was, “How will social media impact traditional BI?”
The snapshot below of what we talked about is posted on several of Forrester’s blog spaces. We’d love to hear your thoughts on this intriguing topic. Share them here, and, if you’d like to hear more about this and other important BI questions, join the discussion on Twitter this Thursday (May 13th, 2-3pm ET/8-9pm CET). We’ll be using the #dmjam hashtag.
Platform-as-a-service -- application development platforms running in clouds -- are entering a new phase of evolution, and not a moment too soon. I've become interested in a new set of products I'm calling "adaptive PaaS" (for lack of a better term) that I think will make the benefits of cloud computing available to a lot more development shops. I'm doing a webinar on this topic May 20th with Appistry's Sam Charrington. I hope you can join the discussion.
As I described in my early reports on PaaS, these products include full development tooling, runtime services, and administration and management tools. While complete, most of these "full PaaS" products are best for new applications, and they incorporate much proprietary technology. Consequence: Many if not most clients are still saying "no" to PaaS for two reasons.
Lock-in: PaaS products lock up your code in a single provider's environment.
Poor fit: Too many PaaS products just aren't strong for core business applications, particularly for rehosting existing applications.
These limitations often prompt developers who want the flexibility of cloud computing to use IaaS platforms like Amazon EC2 instead of PaaS. With IaaS, developers can code in the language and frameworks they choose, reducing lock-in and ensuring a good platform-application fit. As a result, while we see both interest and adoption of software-as-a-service (full applications) and infrastructure-as-a-service (virtual servers, storage, and networks), PaaS is lagging in adoption.