QlikView Vs OLAP – Comparison based on resource required and “Time, Cost & Value”

One of my blog reader “Ms Kaladevi” have asked me the question bellow I decided to answer it as another post on my blog

"I am presently working on a business case for BI project. How do you compare Ms BI tool with QlikView?I case of an Enterprise wide BI project which has to build information from multiple applications...how does this approach w/o data mart work? How will be the performance? "

If I would compare QlikView with traditional BI architecture with QlikView then I can compare on two points.
1- The resources required
2- Time, Cost & Value
If I am comparing on 1st point what are the tolls and resources I require to built entire BI suit.
1- The first thing you require is an ETL tool then you require expertise on ETL who are really a costly resource
2- Then you would require software licenses to create data warehouse &data marts also you need multiple man power to create this data warehouse & data marts which have their own cost
3- Third layer would be your OLAP,Querry and reporting tools & obviously it has its own cost and require expertise to implement this
4- Finally you require to buy an GUI editor and work force to implement GUI
I can draw this like Bellow
Datasource(s) ---(to extract ,transform and load)-----> ETL tool-------> Data ware house & Data Marts-------> OLAP,query & reporting tool ( i.e. your BI software)-------> A GUI editor.
All tools are different and mostly from different vendors require multiple resources to implement, maintain and these projects are highly IT driven.
Now if you look in QlikView it is a single tool having all BI capabilities inbuilt in it like Integration, data compression, Analysis engine, chart and reporting engine and finally user interface.
All in single tool require no costly resources single tool single vendor and it can be implemented by a person who know SQl scripting. QlikView implementation does not require a pool of man power.
If I compare on second point "Time, Cost & Value".
1- Traditional BI projects take at least 4,5 months to show first usable analytical report in QlikView project you can start delivering applications from day one so a average implementation time is 10 day for QV project.
2- Since they are dependent on Cubes you require to built multiple cubes and it is very difficult to provide transition between two cubes e.g. if someone is looking at finance cube for AR report and he need to see details of sales rep associated with a particular customer he need to go back to sales cube.
3- In case of requirement change i.e. if end user require another dimension in cube that is not available in cube or he want to delete a particular dimension it is require to make change in cube it take time to change and for that customer have to be dependent on his BI vendor it has its own cost.
QlikView is based on Associative data model and it is very easy to make change in QV application at any point of time. On demand in time since it is easy!!! This is what I feel is USP of QlikView.

Finally I can suggest that two understand QlikView best way is “Seeing is Believing” or “SiB”. Call your nearby QV vendor for a SiB on you data and see how it is easy to create an application in QlikView what is the performance and how much time you require to implement.
For ‘Sib” you can contact me at sudhir@iconresources.com or call me +91-9312667720