There’s an excellent post by Curt Monash on the underlying technology of Qlikview. Nothing really new, but a very nice summary of how it works, with comments from (among others) TDWI’s Wayne Eckerson and Håkan Wolgé (the author of qlikview 1.0 code and still chief architect at Qliktech).
One thing really new to me was the following part and I quote: Read more of this article »
There is a very interesting interview with Nigel Pendse on the blog from Rittman Mead Consulting. Nigel Pendse is a business intelligence and OLAP analyst and the editor of The BI Verdict (formerly The OLAP Report) and author of The BI Survey (previously known as The OLAP Survey). The interview is about the BI tools market in general, but with a specific paragraph containing some good comments on Qlikview, in memory analysis and powerpivot. Nigels most important conclusions: Qlikview is blazing fast, easy to use and aimed towards the business user, but less useful in large enterprise deployments. Powerpivot is, according to Nigel, just a way to push upgrading to office 2010, the all new vertipaq in memory engine is very impressive and powerpivot isn’t able to handle very complex Analysis Services cubes. Read more of this article »
Today I read this beautiful explanation from Barry (see this link for the whole discussion) about what makes Qlikview different and why it is becoming so popular:
“If this sounds like just more product hype, I apologise, but it is the way it is. QlikView uses a patented technology called Associative Query Logic (AQL). Lets first look at OLAP technology: OLAP-based Hypercubes limit users to a small number of dimensions. Measures have to be defined when the application is developed and redefinition of a measure is time-consuming. The user interface is complicated for non-IT people to understand. If you want to ask questions of a different data set, you have to look in another cube, or you have to reverse out of where you are and start again. No amount of RAM will change this fact. Read more of this article »