This year SAPPHIRE officially changed its name and became SAPPHIRE NOW. Why? Different answers from different people. Those that should know said: "The new name stresses the urgency." Urgency for whom, SAP? And will the next SAPPHIRE be named SAPPHIRE THEN? Never change a successful brand.
Another premiere for SAPPHIRE was the simultaneous show in Orlando, US and Frankfurt, Germany. With 5,000 attendees in Frankfurt, 10,500 in Orlando and 35,000 online participants, this was the biggest SAPPHIRE event ever. I must admit I was concerned going to Frankfurt while everyone in Walldorf desperately tried to escape to Orlando. Who wants to attend a second-hand event? But now I’m a believer. SAP managed to balance the important parts of the show between Orlando and Frankfurt. Keynotes were held simultaneously in both locations via virtual video connection and speakers in both cities. In general I never had the feeling I would miss anything important in Frankfurt simply because it was the smaller event overall. It didn’t make a difference if I couldn’t attend another 400 presentations in Frankfurt or 800 in Orlando from the total of 1,200+ presentations – I had a packed agenda and got all that I expected and needed, including 1:1 meetings with SAP executives like Jim Snabe. The simultaneous, virtual set-up not only helped to save a lot of cost, it created a sense of a bigger virtual community and underlined SAP’s ambitions for more sustainability. To all that traveled intercontinental: Shame on you, next year stay in your home region!
Like every show SAPPHIRE 2010 had its stars as well:
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.
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.