topic Re: qlikview limitations in QlikView

qlikview limitations

Wed, 25 Nov 2020 16:16:04 GMT

In what scenarios Qlikview is not good choice to use

Re: qlikview limitations

MK9885 — Tue, 13 Dec 2016 14:32:34 GMT

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.

Re: qlikview limitations

Anonymous — Tue, 13 Dec 2016 14:45:15 GMT

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.

Re: qlikview limitations

Chip_Matejowsky — Tue, 13 Dec 2016 15:36:53 GMT

Need some context to your question in order to provide an informed answer.

Re: qlikview limitations

sudeepkm — Tue, 13 Dec 2016 20:16:29 GMT

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.

Re: qlikview limitations

Anonymous — Tue, 13 Dec 2016 21:05:30 GMT

If you ask a sales person from one of Qlik's competitors, then I am sure they would happily point out the odd niggle.

Re: qlikview limitations

rwunderlich — Wed, 14 Dec 2016 00:45:44 GMT

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

http://masterssummit.com

http://qlikviewcookbook.com

Re: qlikview limitations

ramasaisaksoft — Wed, 14 Dec 2016 04:31:39 GMT

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.

What are the limitations of qlikview? - Quora

Re: qlikview limitations

varshavig12 — Wed, 14 Dec 2016 06:45:39 GMT

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

Re: qlikview limitations

adamdavi3s — Wed, 14 Dec 2016 08:25:21 GMT

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

-->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!

Re: qlikview limitations

rwunderlich — Wed, 14 Dec 2016 19:25:13 GMT

"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)"

I would dispute that assertion. Large expressions and large amounts of data can perform very well. Poor performance is more likely cause by what's in the expression or how the data is modeled.

"(Every time we need to write those expressions into variables and call variables directly)"

If you mean defining the variables with a leading "=", that can be a bad idea,

-Rob

Re: qlikview limitations

adamdavi3s — Thu, 15 Dec 2016 08:42:23 GMT

rwunderlich‌ for my own professional interest would you be kind enough to expand on

"If you mean defining the variables with a leading "=", that can be a bad idea,"

Is it just the point at which or how they are calculated?

I've always defined variables as sum(blah) (Rather than =sum(blah) ) and then expanded, as it is how I was taught but I've never actually researched why!

I have had a search here and on the cookbook of course but I am obviously not using the correct terms to return an explanation

Re: qlikview limitations

rwunderlich — Thu, 15 Dec 2016 19:09:51 GMT

If you define an expression in the variable with a leading "=" such as "=sum(blah)", the value will be calculated only once, over all data. If the expression needs to be computed over chart rows, then define without the "=" so the calculation is deferred to the chart. So it depends on where the calculation should be done. See The Little Equals Sign

My comment to the poster was more of a guess. I wasn't sure I understood the comment, but was taking a guess at what he was suggesting, In my tuning practice over the past year I've come across examples of people coding KPIs in variables as "=sum(blah)" and then referencing the variable value in a sheet object. I've experienced performance problems with this approach.

-Rob

http://masterssummit.com

http://qlikviewcookbook.com

Re: qlikview limitations

adamdavi3s — Mon, 19 Dec 2016 07:19:14 GMT

Perfect thank you for taking the time Rob

Re: qlikview limitations

praveenkumar_s — Tue, 20 Dec 2016 07:28:22 GMT

what is difference between personal edition and liscensed version...what are the feauture is established in liscensed version of qlik view..let me know as im new to qlik ivew..

Re: qlikview limitations

adamdavi3s — Tue, 20 Dec 2016 07:34:17 GMT

I would suggest using the search button at the top of the page. This has been discussed countless times before.

Alternatively I would suggest starting your own discussion rather than jumping on an existing thread.

All About Qlik Community