QlikView Reviews

• The way data is loaded, transformed and stored in one single file with a high compression rate
• The development flexibility allowing almost any type of relationship between data from disparate sources

Uniformization of KPIs across all departments brings efficacy and effectiveness to coworkers in problem solving.

Performance at front-end level could improve but usually there is a workaround - by reducing application size, splitting applications or the way the UI is presented - without affecting user experience.

I have used it for two years.

There can be issues in terms of stability during usage peeks. In these situations, the server can experience short down times. Again, many of these situations can be prevented by using the best development methodologies.

Technical support is very good. They are always available on providing guidelines.

There are other data visualization tools similar to QlikView. Spotfire, for example, has incredible UI possibilities, but I think QlikView is very ahead in the competition in terms of solution flexibility.

QlikView setup is very straightforward, only requiring server parameterization in terms of ODBC and the QlikView Server. It is not complex when compared to similar products.

It was implemented by an in-house team; some persons on the team had previous experience with QlikView. The learning curve is very quick, but the best practices provided by Qlik must be followed from the beginning of implementing the QlikView architecture.

Due to the quick development of QlikView applications, best practices cannot be disregarded. (For example, load only fields/tables that users need to be available in the application’s layout. When the number of applications starts to increase, this can seriously affect user.

I use QlikView to combine data from different sources in the absence of an EDW and build our analytical dashboards.

It allowed us to improve our analytical abilities, and KPI and data presentation, in addition to creating easily accessible what-if scenarios for decision making.

The security features in QlikView are not yet mature: very complex to define permissions in a dashboard (based on data/sheets).

We have been using QlikView for the past five years.

QlikView relies heavily on memory. It requires good servers and continuous upgrades and maintenance for sustaining good performance.

Technical support is good.

Most solutions like SAS, Tableau and others require a fully-fledged data warehouse (EDW), and IT support and intervention at all times for creating dashboards. QlikView is flexible and allows users to create their own reports in a relatively short time.

The initial setup was supported by the company and was not very complex.

Licensing in QlikView is a bit expensive.

I would recommend the QlikView tool for its flexibility and good data visualization and presentation.

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.

Qlik's data modelling is very powerful and allows for easy integration of data from multiple sources. The in-memory associative engine is very powerful and provides quick answers to questions that arise when a user is exploring their data.

QlikView provides rapid insight that takes significantly longer to reach when using some other traditional BI tools.

I would like to see the desktop user interface updated. Some of the dialogs in the product look quite dated. I would also like to see the responsive UI design features from Qlik Sense make their way into QlikView.

On the analysis side, I would like to see tighter integration with R, or perhaps some built-in machine learning algorithms.

I would also like to see Qlik products made available on other platforms such as Linux and OS X.

I have used this solution for 8+ years.

QlikView is an in-memory product, so large dashboards place a significant load on a server's memory. This needs to be carefully considered when sizing your environment.

I have used a number of competing products such as Cognos, Tableau, Power BI and SAP BusinessObjects.

QlikView development projects are rapid and the product itself is very flexible and reliable.

Initial setup of QlikView tends to be fairly straightforward, though when setting up additional features such as clustering and publisher features, this can get a little complex.

I have implemented the solution both with vendor teams and in-house. In a previous job, I worked with a vendor team, and have worked for a partner and provided implementation support for clients.

I would advise new Qlik customers to seek out a reliable Qlik partner to help with implementation.

I would advise you to seek out a local Qlik partner. They will be able to support your training and consulting needs and provide guidance regarding best practice for your implementation.

QlikView has some superb, unique features but the desktop edition suffers from having a rather tired user interface. Default chart settings can often result in unattractive dashboards, which require significant adjustment in order to conform to best practice. These UI shortcomings have however been addressed in Qlik Sense.

The data model and the visualization are the most valuable features of the product. The data model helps my organization to recognize and identify the problem of our clients’ data. The visualization helps us to deploy an easy-to-understand solution to the client and they are able to explore the data by themselves.

We actually help the client to deploy and design the solution. It helps us to understand their problems better and provide a more intuitive solution. Plus, after the deployment, the client is able to explore and maintain the application without any further charges on the software itself.

The visualization charts. I believe they are working on that because Qlik Sense has released a few versions in which the charts are a lot better than QlikView.

And the interface. QlikView is mainly defined as a guided analytics tool, which requires experienced users to help with the development. In the future, it should move forward on self-service (the core value of Qlik Sense), which is the trend on the business intelligence development. So I think they will have some big changes coming.

I have been using for about one year.

I haven’t come across any fatal issues with deployment, stability or scalability so far. However, as the data volume increased, the skills of optimizing the tool need to be more advanced.

Technical support are quite helpful. We are a Qlik partner and they are willing to help out with issues. Sometimes, they ask for feedback when a new version is released.

It’s straightforward and very detailed documentation is available; just follow the instruction prompts when you install the software.

I also tried Tableau. I believe they are targeting a different market, if you compare Tableau with QlikView. The better comparison will be Tableau to Qlik Sense, which is beyond the scope of this review. The reason we selected QlikView is its relatively comprehensive functionality.

• Connect to multiple sources of data without needing ETL prior to load
• Ability to create complex data joins within the script
• ETL features
• Ability to do complex customization in the design and data representation (set analysis)
• Associative search capabilities

• Scalability
• Live connections
• Responsive design

I have been using QlikView for four years.

Customer service and technical support are very good.

Among Tableau, QlikView, and Qlik Sense, I prefer QlikView, due to its higher customization capabilities, its associative nature, and its ETL features.

Initial setup simplicity or complexity depends on the project and the systems already in place. As for the tool itself, initial setup is straightforward.

I have implemented it in-house and with a vendor team. Business needs need to be fully understood and documented. Most of the issues have always been data related. The development team and the business HAVE to get a full understanding of what the data is, where it is stored, and how it is stored. BUSINESS RULES and a DATA DICTIONARY are a must.

Standardization in design/development is crucial. FULL communication and documentation with EVERYONE is needed. I don’t know how much time has been lost or efforts duplicated because of a lack of all this.

• Intuitive data insights and standard reporting.
• It runs in-memory so you can increase the speed by increasing RAM, depending on your budget.
• It has its own ETL tool, QlikView Connector.

It gives intuitive data insights to improve and optimize our global supply chain (help drive and build strategy to improve on-time delivery, reduce quality and damage returns, etc.), with a few simple clicks to drill down to the details (down to the SKU level and call centre conversation details with customers). The dashboard gives management a holistic picture on our important KPIs.

• Enhance predictive analytics and big data; this is the future trend.
• Simpler, cleaner charts and visualization (easier user acceptance)
• Formatting and repositioning the menu/charts takes a bit long. It does not have drag-and-drop capability like Tableau does.

I have been using QlikView for 2.5 years.

There’s no version control, which means you can't roll back to earlier versions once overwritten/published.

I rate technical support 6/10.

I also evaluated MS BI and tableau. Compared with MS BI, I find Tableau and QlikView have stronger visualization; intuitive data insights; less development lead time - MS BI requires creating OLAP cubes, which takes more time; clearer and simpler charts; and intuitive data mapping/insights.

Initial setup was straightforward.

We implemented it in-house. QlikView is running in memory, so it depends on your organization to achieve the balance between cost of server RAM and performance. Besides, the data quality and accuracy is very important, no matter what powerful visualization tools are used.

Tableau seems to have easier user acceptance than QlikView because of the simpler charts and big data integration, increasing the possibility of helping an organization transform from reactive analysis to predictive analysis.

Server versions are not cheap and pretty similar for both Tableau and QlikView in terms of price. I don't see a big difference; it really depends on your organization's need.

If you have more developers/technical people and want to do more standard reporting without Hadoop, go for QlikView; if you have more business users with some SQL knowledge and would like to do predictive analytics, and integration with big data platform Hadoop, go for Tableau.

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.