What users are saying about

QlikView

533 Ratings

QlikView

533 Ratings
Score 7.7 out of 101

Add comparison

Likelihood to Recommend

QlikView

QlikView is well suited for scenarios where a heavy data is involved or heterogeneous data is there which also requires some manipulation/ cleansing or application of business rules. Also, if the UI dashboard involves complicated formulas to be worked upon, QlikView is well suited.However, if there is a need to quickly create some dashboards where the developer has little knowledge on database/ scripting and also there is no data manipulation required for input data, other technologies other than QlikView can be considered.

Feature Rating Comparison

BI Standard Reporting

QlikView
7.3
Pixel Perfect reports
QlikView
7.1
Customizable dashboards
QlikView
8.3
Report Formatting Templates
QlikView
6.4

Ad-hoc Reporting

QlikView
7.2
Drill-down analysis
QlikView
6.7
Formatting capabilities
QlikView
6.9
Integration with R or other statistical packages
QlikView
8.5
Report sharing and collaboration
QlikView
6.8

Report Output and Scheduling

QlikView
7.0
Publish to Web
QlikView
6.7
Publish to PDF
QlikView
7.5
Report Versioning
QlikView
6.7
Report Delivery Scheduling
QlikView
7.2

Data Discovery and Visualization

QlikView
5.7
Pre-built visualization formats (heatmaps, scatter plots etc.)
QlikView
6.2
Location Analytics / Geographic Visualization
QlikView
4.0
Predictive Analytics
QlikView
6.8

Access Control and Security

QlikView
7.7
Multi-User Support (named login)
QlikView
7.6
Role-Based Security Model
QlikView
7.6
Multiple Access Permission Levels (Create, Read, Delete)
QlikView
8.0

Mobile Capabilities

QlikView
6.9
Responsive Design for Web Access
QlikView
7.9
Dedicated iOS Application
QlikView
5.3
Dedicated Android Application
QlikView
6.4
Dashboard / Report / Visualization Interactivity on Mobile
QlikView
7.8

Pros

  • in memory application
  • AQL i.e auto association
  • QVD
  • conditional hide n show feature

Cons

  • Qlikview has its own database and management system. Developers are required to build a new data model to get data into Qlikview.
  • Qlikview's web application requires significant memory and processing power from the browser. Complex dashboards can crash your browser if you're running too many things at once.
  • Qlikview dashboards look relatively outdated.

Likelihood to Renew

QlikView8.8
Based on 29 answers
No longer with the company. I think the product usage died after I left. Personally, I would definitely support renewing the product if I were still with the company. I do wish they would get off the annual subscription model though and allow for a more straight purchase of the product

Usability

QlikView9.8
Based on 6 answers
Dashboards are easy to use. They are very Excel-like with HTML5 capabilities. Data visualization is good.

The system requires minimum training to get user up and running. It just takes one hour to get up and running with building basic dashboards and one all day session for sophisticated dashboard building. It is intuitive.

We see this in our user adoption. We went from 6 users/day consuming dashboards to over 200 in 1.5 years.

We have 40-50 power users authoring dashboards. They have development licenses. My team in IT used to have to build all dashboards. Our capacity has grown from 3 to 50. Most of these users are analyst types good in Excel. A few power users can write SQL to build QVD models

Reliability and Availability

QlikView9.8
Based on 4 answers
We have not had any downtime issues with the product nor uncovered any significant bugs

Performance

QlikView8.6
Based on 4 answers
It is not a SAAS product.

Support

QlikView2.1
Based on 7 answers
Qlik does have a tendency to push back sometimes stating that the issue is not related to QlikView but the system it is hosted on

In-Person Training

My team attended, but I cannot myself rate, but I think it was good as they've successfully launched a training program at our company themselves for users. It was 3-4 day training.

Online Training

QlikView8.0
Based on 3 answers
Training was as expected. The demo environments tend to be more fully featured that our own environment, but the training was clear and well delivered.

Implementation

QlikView7.4
Based on 13 answers
Not involved.

Breadth of Deployment

Not applicable to our firm as we are small consulting firm.

Alternatives Considered

Our shortlist included Tableau, a newer version of Microsoft's SSRS and Qlikview.

We also knew what Micro Strategies and Business Objects had to offer from our experiences with them at other companies, and knew what we could afford. We eliminated them on price and the complexity of set-up.

We liked QlikView's in memory, associative model, and self-service capability.

With "in-memory", everything that gets consumed from a dashboard is loaded in memory so it is incredibly fast. Although Qlik touts its mobile distribution capabilities, that was not a huge differentiator for us, but is something we are now exploring. Microsoft and and BO do have in-memory capabilities now.

The associative model is patented by QlikView. Basically it starts to understand the associations in your data, e.g. if A=B and B=C, then A=C. It means you can build a Qlikview model very quickly. In traditional data warehousing, you work with users and understand their requirements, refine the data model, start to physicalize it, tune it, build ETLs. It's a 3 month at best delivery cycle. That doesn’t work here at this company. Our business users will not wait for you. Our business is dynamic, we are launching new products all the time. Instead of going through an arduous process, you just load data into QlikView and build an associative model. It link things up. If it doesn’t work, you can change things very quickly. You don’t have to write data definitional language. Where you get into trouble, is if you load very large data sets into QlikView, memory not as abundant. They are releasing a tool called data explorer which allows you to do a hybrid approach – load some in memory and some in database. If data is going into frequently used dashboards it goes into memory. If infrequent access is required and the data set is very large, it makes sense to leave it in the database.

We also have a company called DataRoket that builds connectors for us, e.g. load this relational data into QlikView. They have built adapters for QlikView-Hadoop integration

Collaboration and Sharing

QlikView6.3
Based on 21 answers
Via accesspoint users can share sessions
Add annotations and share bookmarks via email

Data Integration

QlikView8.9
Based on 21 answers
QlikView can connect to almost any datasource

Return on Investment

  • Speed to market is the really big thing. You can attach to multiple data sources quickly and build a consumable model for a dashboard. It doesn’t require IT talent to build. We have built more dashboards and added more users in the last year, then in our entire history. I was at a company of 30k+ employees before, and we didn't have near this level of BI adoption.
  • As a result, we are seeing benefits across business function. For example, within sales, our pipeline has much more visibility. It allows for much faster decisions on things like quotas. One of our biggest power users is in sales ops. She feels her dashboards load 10x faster than our previous tool and she can make changes on the fly.

Pricing Details

QlikView

General
Free Trial
Yes
Free/Freemium Version
Yes
Premium Consulting/Integration Services
Yes
Entry-level set up fee?
Optional
QlikView Editions & Modules
QlikView
Edition
QlikView Desktop
Free1
QlikView
Custom2
1. Personal Edition
2. Per License
Additional Pricing Details
On an perpetual license basis, based on server plus number of users. Contact vendor for pricing.