Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
In what scenarios Qlikview is not good choice to use
I honestly do not see limitations in Qlikview.
Maybe the extensions are not that look good.
Ex: Using Geographical Maps ( The map rendering Data points can sometime take long time) depending on your internet connection/amount of data.
-Self service for users
-Screen size doesn't adjust as per the device you use.
There can be other limitations as well but I personally came across this. But overall it is a very good application to use compared to other applications in market.
Every BI tool has its features.
But when you compare Qlikview with other BI tools, Qlikview built uniquely with
In-Memory Analytics,
Associative Query Language,
Consolidating relevant data from multiple sources into a single application.....etc.,
but in qlikview we all have to play around with lot of functions,
where is other bi tools like..tableau not like that.
Need some context to your question in order to provide an informed answer.
from data store point of view.
QlikView creates a symbol table per fields available in the data model.
Each of these symbol tables can at max store ~ 2 Billion unique field values. (32 bit address mode)
In case you have a field which has more than 2 bn distinct values in it then it could be a problem.
I've never tried to load a field into QlikView that might have more than 2 bn unique values in it but it is worth to try and see what problem you might face.
If you ask a sales person from one of Qlik's competitors, then I am sure they would happily point out the odd niggle.
I'll second Chip's question about looking for context to address your question,
The only general scenario I would advise against is real time analysis or operations. For example, managing electrical utility outages where up to the moment information on status, resources dispatched, etc is required. On the other hand it's an excellent tool for historical -- which may be yesterday -- analysis of outage management where you can trend affected regions, time-to-fix, root causes, number of affected customers, etc.
-Rob
Hi Vibhu,
i know some
-->free license ,but person 'x' can't open person 'y' developed application
-->RAM utilization is very high(server side)
-->Application performance comes slow down if bigger expression(Number of lines and logic's) used in front end charts.(Every time we need to write those expressions into variables and call variables directly)
-->default Chart types also less compared to other tools
-->creating Extensions bit difficult and also not that much good
some more explanation you can find in the below link.
Hi Rama,
What I think is,
If they provide the option of opening other's app, Then why will someone buy a Lic
In fact, the personal edition provides everything compared to lic version except this feature.
RAM utilization -- It has a really good compression ratio.
Variable utilization is a best practice.
I guess the available charts are just enough to make a really good app. ( may be some exceptions )
I don't know much about creating your own extensions, Guess, It really needs good coding skills.
Just my opinion
I have to disagree with these points really
-->free license ,but person 'x' can't open person 'y' developed application Its commercial software and we should be thankful we can have a free license at all? Can you have free excel for example?
-->RAM utilization is very high(server side) Depends on your application and its certainly not as limited as some competitors
-->Application performance comes slow down if bigger expression(Number of lines and logic's) used in front end charts.(Every time we need to write those expressions into variables and call variables directly) Depends on your application and its certainly not as limited as some competitors
-->default Chart types also less compared to other tools This one is fair maybe compared with Tableau but not others
-->creating Extensions bit difficult and also not that much good I think they're very good, try creating one in powerBI and then tell me Qlik is hard!