Thursday, May 28, 2009

Drawbacks of QlikView

Dear Readers,

In past few weeks I received some questions from my readers by email and by comments on my post (Specially from Manolo and Kurtulus once Monolo has shown his aggression also due to delay in response) and here I am trying to answer those Question. I am sorry friend for responding late as I was busy with some assignments and was not able to spent time on blogs.

Before I star I am just putting a part of email that I received from my dearest reader Monolo

"Hi Sudhir,

I would like Death to be like you. Just make promises with no execution.

Or did you guys in India stop time and "next 24hrs" still have not passed ?


Here is the Questions and their Answers

Question 1 -
Can you say in which cases QlikView is not the right solution?

Question 2- If QlikView has any drawbacks at all.

Above picture is explaining the different areas in reporting and the user groups who require those reports. If you see OLAP based tools are capable of handling either Queried data or Static Aggregates or Dash boarding needs. But they are rigid in nature and very hard to adopt any change request from end users. If you see there is clear gap between their needs. (Area in picture with white color)

And OLAP based tools are normally handled by highly trained Specialized IT Person or mid level guy. Top bosses still use excel sheets as they are very rigid to learn a new technology.

Then what is the role of QlikView in this environment?

Above picture describe what are the areas QlikView can cover (See Green Area in picture above) when it come to delivering information to end users.

If you see in far left of this picture it is totally white as the companies who still hold their entire data in Excel (It means they have no transaction system or still dependent on Tally) will rarely have such kind of budget to invest for BI so no tool would be for much helpful for them. (But there are some exceptions also like, one of Major KPO in India is holding entire data in excel and using QlikView to analyze their data)

Above picture clearly explaining that what are the areas OLAP can cover QlikView also cover those and what they can't do QlikView can do that also ( See its feeling the BI Gap)

There are some areas of reporting which are Interactive aggregates QlikView Covers this part also up-to 85-90 % ( See Bottom right of the picture) and these areas are very Niche areas and there are some Niche tool which take care of it I know SAS is one of them.
Over all conclusions is that QlikView is the only alternative/ for OLAP based tool and it gives you more than what you have expectation with a BI tool.

And its GUI also is not very much different than what decision makers ( Actually they are those who have more critical requirements than any one at Organization) are looking in excel sheets and that is the reason users can learn quickly how to use QlikView.

Search more on BI on Web

Know the Blogger