New Tools, New Rules
BIScorecard just posted an evaluation of QlikTech’s QlikView, and I confess, this review has befuddled me more than others.
The challenge with new and emerging technologies is in trying to figure out where they fit and whether or not they really are that different. So I find myself thinking about cars and bikes and QlikTech.
When cars first came on the scene, bike enthusiasts were disgusted with those smoke- spewing machines that suddenly stopped working when cars ran out of gas (interesting that bikes are making a comeback in some cities). Sometimes innovations call for new evaluation criteria – with bikes and cars, features like pedals and gears simply don’t translate against miles per gallon. So does “in-memory” BI make criteria like SQL-generation less relevant? Why do you need a data warehouse at all if you can load a full Terabyte of data in-memory?
In talking with QlikTech customers, all enthusiastically declare they have waited years for this level of empowerment from either their central IT group or from other BI tools they’ve tried. Some of their comments are similar to those of Excel users who later (and still) suffer the consequences of spreadmart chaos. Other comments are reminiscent of early MOLAP (Oracle Hyperion Essbase, IBM Cognos PowerPlay, Microsoft Analysis Services) tool users who could build interactive data marts without IT’s involvement.
So is QlikView really all that different or is it just a re-incarnation of personal and departmental analysis tools? I think the answer lies somewhere in the middle. Their best “feature” is the rapid implementation time, without as much data chaos as spreadsheets and with more flexibility than traditional MOLAP tools. Sometimes speed-to-insight trumps a perfectly architected data warehouse and broad BI solution.
By the way, QlikView is not the only product that does not neatly compare to a single module within a BI platform. Tools like TIBCO Spotfire and Business Objects’ recently released Polestar face similar challenges with product positioning. Even advanced visualization tools such as Tableau, Advizor Solutions, and Corda sometimes struggle with articulating where they fit in the BI spectrum.
Regards,
Cindi Howson
Another one is Visokio Omniscope....pure client side in-memory visual solution that scales with available RAM on 64-bit desktops. It focusses on the 'downstream' "tables ready for human consumption" part of the architecture, rather than the 'upstream' ETL data marshalling/cubing part. The presentation/reporting user-facing parts of the established end-to-end suites consist of many lashed-together, bolt-on acquisitions and browser-constrained visualisations that will not drill-down or scale on the desktop. I suggest you add a new combined next-generation server-side in memory plus client-side in memory solution with the established suites. For example, try evaluating a combination of Omniscope downstream and HiQube for upstream (which is compatible with all legacy cubes).
Posted by: Thomas Bate | March 26, 2009 at 02:26 PM