The Cubegeek has gotten some inside scoops that are big news for Essbase fans. The first is open information which I have no compunction from sharing, but it is significant when you think about it.
Item the First: Hyperion & MDX
George Spofford, who is widely acknowleged as the Joe Celko of MDX, has been hired by Hyperion. In that capacity, he is responsible (in some way) for the commitment to MDX in the Essbase product group. It is thus very likely, especially given Hyperion's past participation in open OLAP standards (APB-1, XMLA), that Essbase is going to implement the full set of MDX functions.
Spofford's new book is entitled 'MDX Solutions : with Microsoft SQL Server Analysis Services 2005 and Hyperion Essbase'.
Item the Second: ProClarity & Essbase
I have it on very reliable information that ProClarity is very seriously looking at adding Essbase support to their product line. This is fabulous news to me, having been certified back in 2003. ProClarity guys are top dogs in MDX programming. Back in 2003, they were acknowledged as the people who had made the best (and only) wizards that generated optimized MDX. More properly said, they were the company, along with Panorama, that debugged the Microsoft API for them. I have a good feeling that they're not going to have that kind of headache when dealing with Essbase. I hope Miss B. at Hyperion goes after them so that they feel welcome into the Essbase Ready family.
There have been many times when I would have loved to stick Essbase on the back-end of ProClarity, especially when it comes to iterative development of new KPIs. ProClarity is a sweet front-end and its server layer is very good about handling things other than query stuff - like documents and spreadsheets. It's a low-maintenance middle tier and handles books of reports very well. Anyway, I'll keep my ear to the ground on this one.
Item the Third: Performance
A document exists that shows some performance benchmarks of Essbase ASO vs MSAS. I've seen this document with my own eyes, and it has names on it of real people - some of whom I know personally. Now this document is older than 6 months, and who knows what has changed since then. But the bottom line is clear. ASO kicked MSAS butt.
The notable notes that I took from this was that unoptimized MSAS is fairly crappy. Who knows where it is now, but even after MSAS was optimized ASO queries processed 40 times faster. There were, as always, qualifications on this. When the Hyperion guys say that sub-second queries are the only acceptable queries, parsing 'better' goes beneath the radar of ordinary mortals. However when it comes to benchmarking, this is computer *science* after all, not computer politics.
Additionally, the results showed that MSAS used a lot less disk than the equivalent ASO models. On the other hand the results showed that ASO scaled much better for concurrent queries. So on the whole, for little applications with few users, it's a push which makes cheap (free) MSAS the winner. When you scale up, ASO wins. That means you have to define 'scalability'.
The great thing however is that the what most people will want from ASO is that it does what Essbase used to be unable to do.