Interesting post from Mark Rittman on the Collaborate 08 and the intersection of the Oracle OLAP world and the Hyperion OLAP world.
What interested me was the comment that:
The room was packed - around 170 at last count, with people standing at the sides and sitting in the aisle - which is about 160 more than the average Oracle OLAP talk in previous years
There is also a lot more in the post that gives an insight to the approaches both vendors have under the hood
Whilst on the subject of service packs I have read from the excellent blog of Patrick Husting that PerformancePoint should be getting a Service Pack.
The comments indicate that this should RTM in May with 300 fixes.
I know that the feature set that will form the V2 release is now in coding and work is going on to firm up the specs for V3 so there is a clear commitment from MS to drive the product forward. Will they get there?
EDIT
Needless to say the guys from Adatis are well ahead of me and also have a link that shows that PerformancePoint will be supported on Windows 2008.
EDIT 2
Nick Barclay has pointed to Peter Eb’s Blog which also confirms the SP1 release and some key changes to the way that the Excel add-in works with MDX (Where clauses are in On Pages are out)
I know I am late to the blog but it has been revealed that SQL Server 2005 will be getting a service pack 3! How a product that had already reached 7 cumulative updates could expect to get away without one beats me.
What I do worry about is how many of the issues that are in the cumulative updates and the forthcoming SP have been wrapped into SQL 2008 and how long that product will be held up by marketing before it gets the updates?
There is an interesting post over on the BI Blog on the “The Importance of “Familiarity” to your BI Users“.
Apart from the importance of a high availability of Brownies at conferences, Guy highlights the importance and difficulty of getting people to “use” the BI tools that CIOs are implementing.
I think that such a debate needs to take a step back and examine the definition of “use”. Too often BI solutions are being designed, pitched and implemented with a level playing field approach. The idea being “we must include the ability to do XYZ so we can appeal to the corporate enterprise analyst”. This then creates the usability issues Guy refers to.
My feeling is that the BI industry needs more segmentation rather than the current trend to all encompassing Uber applications. I also question, but have not formulated a definitive opinion, the drive to tie all BI to Excel. Yes management and accountants love Excel but is that really the extent of the user base?
I know in many implementations I have been involved with the end users knowledge of Excel is at the level of rote learning, Click this, enter that, save there. If that is all the users are doing why try and force the BI application to work and fit into this unsuitable environment? They could just as easily learn a new application. In fact a new application freed from the constraints of Excel may be much easier and therefore cheaper and more effective to implement.
So the question remains what is the definition of “use” and should we be tying our applications to an environment that is only really used and understood by 1% (guess) of our target audience?
