QlikView Review

Works well when you have the right hardware to support it.

QlikView is a powerful visualization and data discovery tool, and works well when you have the right hardware to support it. I've seen the users getting excited about the tool, and the usage ever expanding in most places, provided the KPIs available are relevant.

The tool offers much more capability than simple dashboarding - the natve qvd file formats are excellent if you want to do lots of data cleansing and massaging. Due to this reason, clients can avoid having a separate database license for DWH (please note that QV is not a full fledged DWH, though it supports the most wanted functionalities).

QlikView works out to be the best cost effective when the number of users vary between 50 to 250. Users above or below may have its impact on the pricing per user.

In a nutshell, it is a great product to create leadership dashboards setup for any organization size.

**Disclosure: I am a real user, and this review is based on my own experience and opinions.
More QlikView reviews from users
...who work at a Financial Services Firm
...who compared it with Tableau
Learn what your peers think about QlikView. Get advice and tips from experienced pros sharing their opinions. Updated: July 2021.
522,693 professionals have used our research since 2012.
Add a Comment
ITCS user

author avatarit_user70362 (Sales)

Good post Anish, we have found the scripting required can be very time consuming and therefore development times can be long as well. Would you agree ?

author avatarit_user77913 (BI Expert at a consultancy with 10,001+ employees)
Real User

Hi Andy, I agree, however it really depends on the quality of the developer. The problem that many of my clients face from the market is that even persons having 4-5 months experience calls themselves a QlikView expert; and when it comes to actual delivery, he/she suffers. From a learning curve perspective, I would say that first 30% of QlikView scripting is very easy (this gives a false impression of the tool being very easy to master), the next 40% requires 5 to 6 end to end implementations, and the final 30% is the most difficult part. I've seen very few people exploiting the complete functionality of the tool. If you have the right resources, and have developed reusable components over time, the scripting time can be minimized.