How Hyperion will change Oracle
Oracle is evidently buying Hyperion Software. Much like Gaul, Hyperion can be divided into three parts:
- Budgeting and consolidation applications, descended from the original Hyperion and Pillar.
- Essbase, the definitive MOLAP engine, descended from Arbor Software.
- A business intelligence suite, descended from Brio.
The most important part is budgeting/planning, because it could help Oracle change the rules for application software. But Essbase could be just the nudge Oracle needs to finally renounce its one-server-fits-all dogma.
Despite varying degrees of integrated marketing, planning technology has remained pretty separate from operational applications. I don’t think the reason is UI; Excel-based interfaces work just fine. I also don’t think it’s business process; while I can imagine a lot of ways to screw up operations/planning process integration, I’ve rarely noticed vendors actually making those errors.
Rather, I think the problem is on the data side. “Actual” and “hypothetical” information simply haven’t mixed well. If this diagnosis is correct, Oracle is exactly the right company to finally solve the problem. And the stakes are certainly high enough to get Oracle’s attention — successful application integration could greatly increase market penetration of both the Hyperion and Oracle/Peoplesoft/Siebel product suites.
Essbase, meanwhile, is the definitive MOLAP product. Quite literally “definitive”; Ted Codd’s white paper establishing the OLAP category was commissioned by Arbor. Oracle some years ago acquired the other classic MOLAP product, Express, and painfully integrated it into the core Oracle database; the whole thing has not been much of a success. Microsoft’s separate-server hybrid MOLAP/ROLAP strategy seems to have gone much better.
Essbase sales have been weak recently, and deservedly so. MOLAP’s problem with database explosion produces ridiculous expansion ratios, recent work to lessen the problem notwithstanding. Nonetheless, the Essbase installed base is probably too big and important for Oracle to mess around with (if nothing else, Essbase is the main underpinning for the Hyperion apps). Thus, Oracle may be forced into a multi-server strategy for MOLAP. And if it does that, maybe it will finally offer native XML and well-performing text search as well.
As for Brio: Yet another BI suite? Yawn.
Comments
8 Responses to “How Hyperion will change Oracle”
Leave a Reply
[…] Oracle made a similar move in acquiring Hyperion Software. Mark Rittman and Curt Monash offer their views on this. […]
Hi,
Nothing to do with Essbase or Oracle, but..
I started a new Open Source OLAP project on sourceforge.net/projects/cubulus/ . It can do slice & dice on a web interface, and takes advantage of mySQL 5.1 partitioning.
Cheers, Alex
[…] Oracle, Microsoft и IBM. Essbase окончил в Oracle, посредством Покупки Hyperion. Express уже давно отошёл к Oracle и тесно проинтегрирован с […]
[…] reminds us. It was relational. Eventually, if I recall correctly, it was swapped out for Essbase (the original MOLAP product, now owned by […]
[…] An integrated suite of DBMS, 4GL, and perhaps other tools around a MOLAP architecture. (Examples: The IRI Express and Arbor/Hyperion Essbase products Oracle bought.) […]
[…] me interrupt my tweaking of very smart people to confess that my own commentary on the Oracle/Hyperion deal was not, in retrospect, especially […]
elena likhach wife
How Hyperion will change Oracle | DBMS 2 : DataBase Management System Services
You can certainly see your skills within the work you write.
The sector hopes for more passionate writers like you who aren’t afraid to say how they
believe. Always follow your heart.