QlikView Reviews

It is very simple to use. When I use QlikView, I just install it and then connect it to MS SQL Server. After I make a successful connection, I can, for example:

1. Create a simple procedure in MS SQL Server.
2. Execute the procedure to get the information I need in a column.
3. Design a QlikView report that includes the column from the procedure to preview it in QlikView.

It provides sales and other analysis with good visual graphics.

I would like to see the possibility to change the program if the new program is better than last program.

I have used this solution for just three months, because we don’t have enough employees to manage it.

It requires a lot of RAM on the PC.

We will possibly continue using the product.

It is very easy to install.

The associative/relationship engine and fast performance are the most valuable features of the product for me. It is excellent for number crunching with basic visualizations and known questions.

QlikView is used internally for financially-focused groups. It has moved folks out of Excel land into interactive/shared analytics.

I would like to see improved performance/scalability at high data volumes + high user concurrency. Having only in-memory capability for hosting source data is a constraint.

I have been using QlikView for 2.5 years.

No issues with deployments/stability. Departmental-scope in use has it well-positioned here.

Technical support is very good.

Nothing else was reviewed, given the business area lead had previous experience with QlikView and wanted that for his department.

Initial setup is straightforward. It is not a complex system to install.

We used a regional vendor that had experts in the platform to help us install/configure/jumpstart our use, working directly with the business department in need.

ROI is unknown. However, licensing costs continue to increase in QlikView and in Tableau, which we also use, forcing us at some point to consider consolidating to one and/or turning some existing/owned MicroStrategy licensing inward to replace if the the upward pricing trend continues.

Pick the right tool for the job/consumers of the products. There is not a single product that can cover all personas/use cases well or there would be only one product out there commanding the world – and there’s simply not just one. QlikView is great for numbers-focused users who live in Excel today and want a better way to create common metadata and analytics that can be easily distributed/consumed by target users.

• Combination of ETL with powerful scripting options and a fast, flexible front end makes it like a Swiss army knife
• Powerful front end, which allows us to make very user-friendly interfaces
• The associative model, which allows for truly integral reporting

The combination of quick, agile delivery combined with a front end that allows you to easily drill through from high-level dashboards to low level details means that we can deliver according to the business case. Compared to our other tools (e.g. SAP BO), business users are using this tool a lot more.

• Chart types; some look a bit outdated, would love to see Qlik Sense- or Tableau-like visuals
• Central formula/measure repository, can now only be done with variables

I have used this solution for eight years.

Deployment is very easy and quite stable. Only drawback is that the server can stop functioning if not enough memory is available, so that needs active monitoring once you are close to the limit.

Good, quick responses and mostly the support team is very knowledgeable. You don't have to go through multiple layers that delay the resolution, like with some other products we have experience with.

We have everything, but the combination of functions in one tool as well as the good support and quick implementation times make QuickView our preferred tool for most use cases.

Straightforward, easy installation (next-->next-->next). Single sign on was a bit more complex, but way easier than with SAP BO, for example.

We have implemented it with vendor teams and in-house ones (multiple installations). For a simple scenario with one server, just do the training and you can do it yourself. For a more complex scenario (we have a cluster of six servers in the cloud), it is better to let the vendor do it; they have the best connections for the complexities of clustering.

License prices are quite high; it makes the roll-out slow as you first have to convince people of the benefits. When growing, session licenses are the best; we achieve a ratio of 1:30 for the average user.

Perhaps if you start from scratch, it is better to start with Qlik Sense, as it seems that most development effort goes into that product.

QlikView enables fast visualisation, analysis and navigation through data. It is very flexible, and offers easy-to-develop, quick-value tools for navigating and understanding data.

QlikView allows non-technical stakeholders to quickly engage with and navigate through their data as business information.

Data modelling is often a protracted process, with no toolset available apart from scripting. The consequent data models are not very portable at all.

I have used this solution for five years, sometimes more intensively than others.

One of QlikView's greatest strengths is its in-memory handling of large amounts of data. The flipside to this is some ongoing leakage, which makes it sensible to reboot once a week.

Qlik's support model for everyone except large enterprises is through consultant partners, so it depends on the quality of the partner. On the whole, they seem to be good.

It was implemented via a consultant partner. They were technically very good, but one should ensure the consultant delivers comprehensive documentation. A solution is only as good as the ability to navigate through it and enhance it as the business changes.

Although normal advice would be to mandate that the implementation deliver to business-specific requirements, it is strongly recommended to understand the product's great capabilities, and to exploit the competitive advantages of the product. Otherwise, it becomes just another business intelligence tool blindly shoehorned into a business that doesn't gain the best value and ROI from it.

QlikView’s associative ability. The AQL that QlikView uses to associate and ‘bring together’ similar data types (based on name) is extremely powerful and useful. One click causes a whole ripple effect though the whole dashboard, because everything is associated to one another.

We have used code to create a calendar effect. We then loop through that calendar, executing SQL at the end of each month. This is not easy to mimic in normal SQL, and would require an SQL package to perform such a thing.

QlikView allows us to perform these feats with ease.

QlikView does not work very well with very large data sets. I would like to see that improved.

I have used this product since Jan 2013.

Besides the stability issue with large data sets, I have not encountered any other deployment, stability or scalability issues.

Technical support is 3/10.

I have not evaluated any solution similar to QlikView (e.g. Tableau).

We did not previously use a similar solution.

Initial setup was straightforward.

A vendor team implemented it. They knew the tool best and we could get it up & running a lot quicker. Part of the implementation included training.

Not easy to answer. What we use it for, internal to the company, is to track internal costs as we manage quite a number of cost centers. We've successfully managed our budgets and have recovered quite a substantial amount of money for our CC as QV has allowed us to track incorrect CC billing.

QlikView really works well. We have had no complaints from users about its functionality. There has never (or hardly) been a time where a user makes a comment like “Oh, pity that QlikView can't do this…”

The ability to build models that allow business users to do their own what-if analysis on the correct data.

The business was previously using Crystal running on top of hardcoded SQL stored procedures and Qlikview. Qlikview improves development productivity and allows self-help BI.

I would like to see more ‘drag and drop’ functionality as, in my opinion, there is still too much coding required to join tables correctly.

I have been using this solution for 18 months.

As mentioned, we previously used Crystal as well as Oracle OBIEE and both are inflexible and time-consuming.

Initial setup was very straightforward, plus the team had set up Qlikview previously.

We used a vendor team for implementation and that’s probably the way to go first time around, but there must be a skills transfer.

Qlikview are always willing to negotiate pricing, especially if you mention that you are evaluating Tableau as well.

Don’t believe the sales talk that you don’t need a datamart or data warehouse to run Qlikview on top of. It can run against ERP data but then the queries get very complicated and cumbersome.

It allows you to establish business data models on an associative basis, and to do on-the-fly analysis on associated data for deep understanding / insight.

For complex analysis, its scripting capabilities enable one to do complex calculation to present required information much easier than traditional / other BI software.

I have implemented both QlikView and Qlik Sense solutions for our customers/organizations in multiple industries.

The immediate improvements allow organisations:

• To analyse data more comprehensively (e.g. in the areas of risk management and customer profiling/segmentation) to provide greater insight / understanding
• To make data available more quickly to facilitate decision making, especially for exceptional cases (e.g. when not meeting KPIs)

Other side benefits derived from implementing such projects are:

• Data gaps: It can identify insufficient or unavailable data for making better decisions.
• Process gaps: It can identify business processes that need to be improved, e.g. manual processes that need to be fine-tuned or automated.
• System gaps: It can identify areas where the system needs to be improved e.g. improvement to existing system functions, or a new system needs to be put in place.

With such gaps and their relationship to the values of decisions, an organisation is able to prioritized resources to address those gaps over time.

Improve its table/data editor to allow easier ways to pull multiple data from multiple sources and associate them to establish a complete business data model.

Consider providing more features that allow the decision-making process of analysing different data at different levels to be captured. Maybe a decision-making flow/process editor for Qlik sheets and objects at the presentation layer.

I have used QlikView for approximately five years.

You can encounter deployment issues if you do not follow good / recommended “best practices”. Such issues can always be resolved through better design of the implemented solution.

By adhering to good practices, deployment, stability and scalability should not be an issue.

Technical support is average.

Initial setup is straightforward and much easier than other traditional BI software.

We are a Qlik implementation partner. We implement Qlik solutions for customers.

Our customers’ ROI is typically within 1-3 years, depending on the size and complexity of implementations.

Initial pricing/licensing of QlikView and Qlik Sense are competitive to the market. However, as the number of users grows, it could be costly.

You need to understand well the users’ decision-making process, the data requirements and the actions users want to take. It is OK to start a Qlik project without complete data available.

The associative engine and feature-rich expression scripts are the most valuable features of this product.

Easy, low-TCO solution to consolidate and visualise data for analysis and reporting purposes.

It provides better visibility of the company's position and its operations.

I would like to see more visualisation objects features.

I have used QlikView for more than a year.

I encountered minimal deployment issues.

Technical support is excellent.

I have experience with other similar visualizers, but QV offers a better experience in terms of ETL development.

Initial setup was straightforward, with a simple, easy interface. We had a simple setup anyway, not much complexity. We were able to get QV up and running in a very short turnaround time.

It was implemented in-house assisted by a lean vendor advisory team.

Data mining and consolidation are the products most valuable features to me.

I was using this to track KPI’s on my outsourced end user support (ticketing, resolution & time it takes to resolve). This forced my contractor to deliver because QlikView provides an analysis of the issues as they appeared.

I would like to see improvements to scheduled reporting and the capability to email the user.

I have used this solution for over four years.

I was using the cloud-based solution, so I didn’t have any issues.

Technical support was super, can't complain.

I had used other solutions, but they didn’t give me the kind of reporting & analysis I got from QlikView.

Set up was easy. Being technical, I found it easy and straightforward.

For our installation, we used the vendor. However, for my peace of mind and understanding, I was involved throughout the process.

ROI was not a consideration for me, though I would would say it was a great tool I would have equally gone for, even if it involved doing the ROI.

My use was more about service measurement & improvement.

The dynamic interactive dashboard is the most valuable feature of the product to me.

Lots of scripting used to be required to build high quality dashboards.

This cannot be considered a self-service product. It requires IT support.

I have used QlikView for one year.

This is quite a stable product, but very huge data loads must be complemented by good hardware. Otherwise, there could be performance issues.

Technical support is OK.

The only reason we chose this product is its dynamic interactive dashboard. It works well on iPad. We liked the product, as compared to MS BI.

Initial setup is quite straightforward, but it requires good hardware for high data loads.

An in-house team and a vendor team collaborated on the implementation.

It is quite expensive. There are two types of licenses: Named User licenses and Doc CAL licenses.

You need to have good scripting skills.