QlikView Reviews

• ETL functionality is hugely important, as data rarely are provided smooth and clean, even when the assumption is it has been cleaned beforehand. Plus, usually in BI, we need to create custom groupings, and being able to do that in script ad-hoc is very helpful
• Scripting for loads, with lots of functions, and insert script possibilities all provide extremely good flexibility for development.- Overall flexibility and ease of development is great for ad-hoc quick fixes, quick workarounds, which happen in BI
• Set-analysis function, unique for QV, is an awesome way to create subsets, literally under any chart/table/text box needed in a smart, fast way (replaces long expressions such as “if...then...“). It also allows you to control results, taking into consideration user clicking and selecting data.
• Associative model is super handy to just take an overview of data quality through visual associations (power of grey).
• Data governance is an extremely usable feature; there is no need for BI to build its own app, and it helps with licence monitoring.

With QV, literally all departments across the company have started “owning” data in terms of getting hands on data, knowledge about data, how it is built up, and the ability to slice and dice, add, expand, or decrease the size or granularity of their own reports.

This in turn has in general decreased the “fear” of touching applications on computer. With backups maintained by IT, people are given more freedom to try and change applications themselves.

Regex. Cleaning out data during script regex could be really handy.

Otherwise, I am having a hard time thinking of any other areas with room for improvement.

I have used QlikView 9 for two years, I am trained and certified on
QlikView 11, and I have used QlikView 12 for half a year.

I have not encountered any deployment, stability or scalability issues.

I have not had direct contact. Currently (with Qlik Sense), I am working with Qlik local partners, not directly.

Before QlikView, Excel was used across the company. At the same time, we had SAS Web Reporting Studio provided by my company’s headquarters, which was very far from even being considered to be used for anything beyond just comparing total sales numbers if the QlikView reports were in line.

I remember it being set up with the first production app running in three days. So, initial setup was straightforward.

Implementation was done in-house.

During the selection of the local BI tool, the choice was between IBM Cognos and QlikView. We were naturally showcasing to management how easy it is to use the UI, and the latter one was chosen.

I think it is the best BI product out there, competing only with its own “brother” Qlik Sense. (While the latter is not that mature yet, it is definitely growing in power extremely fast.)

QlikView is a good choice!

Data exploration and in-memory capabilities: It has an associative data exploration feature and can handle one hundred million lines of data and provide good performance.

N/A. We are consultants.

Qlik has launched another product, Qlik Sense to improve ease of use for the end user. The product lacks PDF exporting, mapping – which costs extra - and reporting features. Also, it turns the data into QVD format that is not accessible by other software.

We have been using QlikView for five years. We have been a partner for five years as well. We have successfully completed seven QlikView projects.

I did not encounter any issues with deployment, stability or scalability. It is quite easy to install, configure and deploy.

QlikView has a very good developer community where you can find support from the other developers.

We usually position this product for departmental and fast-win solutions. When you’re an expert in this product, it’s quite easy to develop well-functioning and complex dashboards.

Initial setup was quite easy.

QlikView has CAL and Document CAL licencing. It’s quite cost-effective when lots of end users use several reports like once a month.

If you plan to develop dashboards and want the end users to further develop the dashboards, it requires some IT skills. If the end users should develop their own reports, Qlik Sense should be chosen.

It allows our company to view all of our data in a single solution. It is easy to use, even for novice users.

The product has reduced the number of reports that were previously constructed manually by users. It also allowed us to prepare a single report using a common data source for all users.

In QlikView 11, there is a password for the section of code, but there is no user management with a password that allows access to data when opening the file.

I would like the data loading and programming to be made easier.

I have been using it for five years. Currently we're using v11.20 and testing v12.

The product installed at the time did not present operational problems or stability issues.

The consultant company that sold us the product provides us with follow-up service. At the moment, we are satisfied.

I used BOARD at another company. I have found QlikView to be better.

The initial setup was very simple and in a few days, we were able to begin operating with the data available.

We developed the solution partly in-house and partly with the supplier. We took responsibility for the preparation of the database, retrieving information from the management system and preparing it in a suitable format, leaving the supplier responsible for the implementation of the loading from this database and reporting.

We are happy with the product. With regard to the license fee, for a customer, it is always better to pay less.

It is possible to work with a large amount of data without affecting the performance.

It improved development, because we could just put our data into it and start working, even with datasets with millions of records. Its high speed has also improved my organization.

It would be great if this software had better transforming tools. We can do a lot of heavy work with scripts, but sometimes that gets really messy.

I mean that it would be very good to have a graphic tool to manipulate the data.
I work with IBM Modeler, and I love how easy it is to transform data in it. I think QlikView could implement a graphical interface to manipulate date, just like Modeler. I also think thats way off the scope of QlikView, but I am just thinking how great it would be to have such tool built in.

I have used it for four years.

I haven’t found any problem with deployment, stability or scalability yet.

Technical support is very good. Every question I had, there was someone to help me.

I started working in my actual job because of this software, so I didn´t have the opportunity to choose it. However, I can see it´s great software, and I´d surely choose it.

There wasn´t any problem with the setup, it was very easy (much easier then Oracle OBIEE).

When I got access to it, it was already implemented. I just upgraded one time, without any kind of problem.

It works as a complete BI software solution for us. We can do complex scripting to build data models. We can make somewhat complex reports, even though it does not have the best capabilities as an ETL tool. It is not the best tool for complex reports. It also does not have the best visualizations, but it has a lot of features in one package, and that is its biggest selling point for us.

Performance is very fast. You can create dashboards for large sets of data and the dashboards are still quite responsive.

Creating dashboards takes a lot less time compared to other big vendor solutions.

In my current organization, we use QlikView and we love it. We feel that for us it still does the best job possible. We want to be able to create
beautiful visualizations like we could with Tableau, but we also know that the flexibility we have in QlikView is not possible in Tableau.

Also, as of now, we have IT-driven BI and self-service is not what we are focusing on. We don’t have separate tools for ETL jobs. We think for our purposes, QlikView is better.

In one word, QlikView has become dated now. Other vendors are providing equal or better solutions, especially for self-service, on-the-fly beautiful visualizations and ease of use.

QlikView is not moving as fast as the market trend. There are no big updates in their product that could make our life easier. As far as the useful functionalities, QlikView is the same as it was five years ago.

They did launch a new tool to compete with Tableau, Qlik Sense, which they are trying to push to customers, but it actually falls behind QlikView. (They know that, but they don’t want us to compare Qlik Sense to QlikView, saying they are two entirely different tools.) We still prefer QlikView compared to Qlik Sense. Qlik Sense is incomplete at best.

QlikView is your one-stop shop for all of your BI needs, and it performs well enough. With one tool, you can take raw data from your database/files and develop the complex analytic apps, which I think is the best thing going for QlikView. It’s very flexible and has matured itself well enough to be deployed organization-wide. The learning curve is definitely higher and you might need your apps developed by IT.

It is good for organizations that don't want to invest in multiple products.

• The associative indexing engine that does away with the need to design and build OLAP cubes. Instead, it can integrate information from multiple sources in one data model that is easy to maintain, expand, and completely flexible to navigate (no pre-defined query paths).
• The out-of-the-box ETL capability that takes care of the necessary data transformations without having to rely on a separate product.

All information analysis, from casual one-shots to continuous tracking reports, is done with QlikView. This lets us see new patterns as they develop, enabling us to react quickly.

Currently, there is no SaaS licensing model.

The ETL tool could use some visual aids in addition to the wizards that help to build the code.

Visualization design is not drag-and-drop.

I have used it for 6.5 years.

I have not experienced any deployment, stability or scalability issues, except when the workload load exceeds the hardware capabilities, which is the result of poor sizing, poor development practices, or unanticipated growth.

Customer Service:

Customer service is almost always spotless.

Technical Support:

Tech support is efficient, but seldom necessary due to the very large and dynamic user community.

We did not previously use a different solution. Choosing it comes naturally because we resell Qlik.

Initial setup is as straightforward as client/server installations go. Complexity can arise when getting access to data sources or integrating with third-party security, for example.

We implemented it in house, because we have a Qlik consulting practice. My advice is to not overcomplicate the implementation with excessive design, because the data model can grow organically over time.

Historically, ROI is best-in class for this kind of solution. My advice is: If you have many users, use the large deal size to your advantage.

Join the Qlik Community, ask around if you have any questions, and hire certified consultants.

Take my rating in the context of a complete Business Intelligence platform: data acquisition, transformation, reporting, dashboards, visualization, analytics, collaboration, mobility, and so on.

The features of this product that are most valuable are: its point and click user interface, speed, ability to follow dependencies in data, ability to fix any view in my special sheet, ability to track back to data sources for any output value or part of a graph.

We implemented an application for control of sales team, for controlling. Accounting people or our sales director are able to work with it without extensive training and they are able to do their own analysis without support of IT people. We developed an application for health insurance company that allows them better control of a cost paid to hospitals or doctors. They have very detailed analysis of drugs paid by insurance.

Areas of this product with room for improvement are ETL, presentation of data on a map, what-if modeling or predictive modeling, license policy.

We are using it for, I think, 6 years.

No. But you should respect such special features when you design a data model.

No issues with stability.

No. But we did not used QlikView for Big data.

Customer Service: The customer service is done by partners. So if you have knowledgeable partner the service is good, if not you can easily switch to another. Our country is small and there are several partners who can support QlikView, so I think that every customer could receive good support.Technical Support: Technical support from QlikTech is at standard level. What is non-standard in a comparison with other tools is the very low number of errors that we found. I do not remember any important error during the time we used it.

We used Microstrategy, Actuate, Crystal Reports. Microstrategy was much slower (all of them) and it had very bad support in our country. All three tools consumed much more days for building the applications – but it was 5-6 years ago, I am not familiar with today’s versions.

It was straightforward, but we have skilled people and we are not beginners. We are an IT company.

We did implementation in-house and we deliver projects for our clients. We have people that passed training in QlikTech.

Day to day cost consists from maintenance fee and we have a man, who is responsible for development of the internal application. But the same man together with other members of BI team are working for the customers. Setup cost was not high. When we started we bought 5 licenses and developed the application in-house, but during the years we have invested in the development of our internal applications. It is a continuous improvement.

We have knowledge of Microsoft Analysis Services, Jaspersoft. We sometimes use Jaspersoft as an embedded reporting tool into application. QlikView was nice and easily to learn, so the evaluation period was short.

To do careful requirements analysis, be sure that you have all relevant data available, start the project with somebody, who has an opinion of QlikView.