QlikView Reviews

• 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.

QlikView Desktop Enterprise allows us to build dashboard visualizations in a fashionable way and allows us to make quick business decisions all over the enterprise.

The improvement was much more related to be able to link different data sources to the same visualization. Now users have access to a one-stop shop for their data queries.

I believe that improved analysis prediction capability would be more than welcome in QlikView. If we could simulate scenarios in a more intuitive way that would be a nice-to-have feature.

Besides the fact it’s quite a useful tool for data visualization, the final user interface is not that intuitive. That might be the idea with Qlik Sense, which we haven’t had an opportunity to experience yet.

Prepare your data warehouse platform. The more time you spend on DW development, the more your users will be able to take advantage of the data analysis.

Data integration and visual drill-downs are excellent.

I work for a consultancy and develop projects for clients. Our clients have definitely got benefits with the use of QlikView with accessibility of their business metrics in an interactive form on their smartphones. Also, QlikView can compress and store data in its own format, which makes it faster after data loading.

• Version changes should be made fully compatible with older versions.
• Advanced analytic capabilities of model building using regression or time-series analysis should also be added in the product.

Client requirements should be clearly understood and limitations of the product should be communicated to clients before making any commitments. Often projects are jeopardized due to poor communication and unclear expectations.

There are two reasons for my rating. First, the interactivity options are limited and, second, modelling options are not available. Also, we faced challenges with version changes and in integrating it with geographical information systems.

Fast development, support for QVD format files, and business discovery are the most valuable features of this product to me.

Before we started using QlikView, we needed to put or clean our data in four steps. Now, we just connect the database, clean it and show the information.

In the next version/release, I'd like to see mashup possibilities and real-time connections.

I have used QlikView for five years, and Qlik Sense for two years.

I encounter deployment issues but it depends on how you develop it and for what are you using this tool.

Technical support provides high-level service.

Initial setup is straightforward; you just install and use.

When implementing through a vendor, be careful with your environment.

This product pays for itself fast.

Try it. You can use just one tool for most of your connections. It's easy to maintain and you can focus on data and decisions.

I think the most valuable feature is the possibility of working with all types of data and sources.

Now, we have all the company´s important information gathered in one tool, so it´s easier to analyze it.

QlikView is really easy to use and it can help you manage different kinds of data, but licenses are expensive.

I’ve been using QlikView since 2011.

We did not really encounter any deployment, stability or scalability issues.

We have a good support here in Ecuador. In fact, we have an SLA with Grupo Novatech with specific times for technical support.

The initial setup was straightforward. There was a small amount of data with few KPIs.

We have an in-house team. They implement some dashboards. If there was a complication, we called Novatech.

I think licences are expensive. I think QlikTech should work to develop a cheaper licence, only to visualize data through the internet access server.

I have not evaluated any different solution. I´ve always worked with QlikView since I´ve been at my company.

I think QlikView is a good tool if your company is not big, because of the licence cost. If your company is big, it’s a good idea to have an in-house team for new implementation or for little changes, because technical support could be expensive.

I think QlikTech is working in the right path to improve the usability of QlikView with the new tool Qlik Sense.

The best features of QlikView are:

• The fast and easy process of extracting data from multiple sources (DB), although having duplicate data in the source files creates a mess.
• The intuitive way of creating dashboards for finance, sales, BPM, etc.
• The display and drill-down access to detailed information, graphic interfaces are easy to create and dynamic using just one pivot table.
• The easy way to grant access to all the data or just bits of it to specific users.
• The capability of QV to handle .pdf files.

As an example, today we have our budget information from different areas in one summary page. Numbers are updated fast and easy in the web browser. This has given crystal clear info for all the users that have access to the model. Hard data and dynamic graphs give a clearer and accurate view of the data. Filtering saves a lot of time when doing presentations to the top executives of the company; any question is answered in real time with just a few clicks.

I would like to perhaps be able to have preloaded and editable examples of models created by QV experts that can be customized for our specific needs, instead of starting from scratch anything we need to work on.

I work an electric utility in Mexico, therefore we build QV models and dashboards specific to our industry (electricity, gas, nuclear generation, asset management, executive reporting and such). 

Right now, we have to build our models from scratch, if we could have access to prebuilt models for our specific industry and line of business it would be very useful and time saving. 

It’s important to understand that the quality of the final data will have a direct relationship to the source of information. You can really apply here the phrase "Garbage in-Garbage out". Because once QV is up and running, almost everyone will turn to the dashboards as THE source of information, it’s imperative to be sure the source of data is flawless.

It’s a great BI tool to convert raw data coming from several different sources into a dashboard full of in-depth knowledge, to do proper information analysis and make accurate decisions for the company.

Usability, usability, usability: It is easy for developers and for end users.

We have cut Fire Department 911 response time 8-30 seconds.

We have improved the timeliness, accuracy, and consistency of reporting.

Unmetered water reports (e.g. fire hydrants, FDCs in commercial buildings)

Wage verification requests

Performance metrics

We have improved processes and increased compliance of firefighter training and certification, ensuring that firefighters are properly trained (“a trained firefighter is an effective firefighter”), expensive training courses no longer have empty seats, and we have improved our performance on training/certification audits from our regulatory agency.

We have engaged line managers on tracking and monitoring of program and operational budgets, leading to better oversight of the taxpayer dollar.

The QlikView management console could have better interfaces for managing security. Right now, it is hard to tell “who has access to exactly what apps?”

Better out-of-the box governance features, to allow analysis of application architecture, optimization of scripts, identification of unused fields/data.

Current GIS interfaces (e.g. with ESRI) are through partners, and are acceptable, but could be easier to implement, more streamlined interface between the two.

I have used this solution since 2008.

No issues at all. This application requires very little care and feeding. Cannot speak to big data scaling, our largest data sets are in the 1TB range — but no problems noted at that level.

Customer and technical support are fine. Account manager deals well with the added layers of demand that come from being a government client — purchasing is always more complicated.

Like everyone, we used Excel and Access. We tried using the enterprise MicroStrategy and both developers and users rejected it as too much effort, not intuitive compared to QlikView.

Technically, initial setup was very simple. The hardest part was getting visualization requirements form unsophisticated users who were not used to any sort of reporting on their processes.

We did it in-house, with one week of one vendor person assisting. (The four apps he helped us put together, we ended up redesigning altogether once we had a chance to use them and redefined requirements.)

Advice: Keep it simple. We know of similar organizations that used third-party implements, who created apps that were complicated to support and use, and consequently those implementations were not entirely successful. In at least once case, they abandoned the product (and haven’t done anything else that I’m aware of).

Qlik has a reputation for being expensive, but our TCO - compared to two other BI products in our organization (MicroStrategy and Cognos) is way, way cheaper. We didn’t have to pay for consultants or any professional services. The more we let our business managers design and develop their apps, the happier they are.

Keep it simple, involve the team (prototype with them - don’t throw a fancy app over the wall at the end users and expect them to actually engage), do POCs before you decide which BI system you will adopt.