QlikView Reviews

We primarily use the solution as a BI tool. We use it for data visualization.

Technical support is good.

The user interface and dashboards are very good. 

There are no issues with management monitoring. 

The solution offers good documentation.

We find Tableau to be a bit of a better solution. QlikView should try to be more like that.

The solution is quite costly.

I'm not sure how long I've been using the solution.

We have our own engineers and support from our tech department, so we've never had any issues dealing with the technical aspects of the solution. That said, they're okay. We're satisfied with their level of service.

We're also currently using Tableau. We find it to be better and easier. It's also less costly.

We want a few things that just aren't available on this solution, so we're moving more towards Tableau as our product of choice.

We have exceptional staff on hand that handled the implementation and deployment. They didn't have any issues with it. For them, it was straightforward. It wasn't complex for their level of expertise.

We handled the initial setup ourselves. Our internal team is very knowledgeable and can handle the implementation of new technology. Adaptability to new solutions is very easy for us.

The solution is expensive to use.

We're just customers. We don't have a business relationship with the solution.

We're actually thinking of moving off it and onto Tableau.

I'd rate the solution six out of ten. It just doesn't offer us what we need right now in terms of functionality. Tableau is a better fit for us.

On-premises

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.

The strongest characteristics of the product are its ease of use and its data discovery and exploration capabilities:

• Ease of use, as it is very intuitive, as long as its back end data model is well designed, providing its end users with a high level of autonomy and the developers with a very intuitive and complete set of tools.
• Data discovery and exploration, thanks to its in-memory data association capabilities that provide a fast and easy way to relate and explore data.

As a consultant, QlikView has helped me deliver high-value BI solutions to my customers, consistently exceeding their expectations and creating new opportunities for my firm.

It could be more mobile friendly, as some of its features don’t work properly on mobile devices or do not provide the best user experience to our customers who would like to extend their access to data. A Cortana/Siri-like feature or advanced analytical capabilities for users with advanced scripting and statistical skills would also extend its usage in the organizations where I operate.

I have been working with QlikView for about 4 years.

I still find some fine tuning issues when scaling up in concurrent usage or data volumes.

Strong customer service, not as strong on the technical part, and the community is still a bit underdeveloped.

I’ve also worked with other main market solutions like Microsoft, or Tableau, but over the last few years, QlikView has evolved considerably, especially when they completed it’s offering with Qlik Sense 2. Although it is not as versatile as the Microsoft solutions, it is stronger in ease of use and development when compared to Power BI for example. It’s licensing costs when compared to Tableau are also a differentiating factor.

It was extremely simple and straightforward to implement.

We do our own implementations without the need for a high level of involvement from the QlikTech vendor team. Our main advice is that a good understanding of how tabular models work when designing the data model, and a good understanding of the full QlikView offering specifically in terms of ETL, are fundamental for a good QlikView implementation project.

BI implementation projects using QlikView are normally faster to execute and faster to get the customer to perceive its value. However, it makes sense to start with a smaller investment specifically on QlikView licensing, as modeling the data and implementing the ETL part is still the biggest bottleneck. It doesn’t make any sense doing a big investment in user licensing, when the real use of QlikView still depends on getting the data to make sense.

Make sure you have your data straight - think like Kimball, but act like Inmon - before moving to QlikView.

As a BI professional sometimes you have to tackle projects with poor or no documentation at all, just the datasources and some vague requirements. In QlikView it is quite easy build up a first data model (dimensional or not) and use the first stage to understand the entities and relations between it and the business. From there you can explore the business, understand the users real requirements and needs and improve the model with a few changes, without much effort. This is because Qlikview has a very flexible and short cycle of development in each iteration.

For the user QlikView is a wonderful tool of data discovery, providing powerful tools to navigate easily between a sea of data in an intuitive, easy, and clear way, allowing them to go from facts to KPI and vice versa.

Qlikview can be used both as an advanced reporting tool as well as an BI KPI tool, becoming the base for continuous process improvements. In general the benefits of the tool become clear at the early development stage when the user is challenged to input clearly his ideas, problems and needs and that will affect the process in which he participates. Typically in a second iteration the key user will ask for a new release more oriented to advanced KPIs rather than just reports. This is a direct consequence of the process making things clearer and evolving. So the main value supplied by Qlikview is to reduce uncertainty, make the participants question, discover, interact with each other, and eventually improve the process. Properly used should function as an improvement catalyst for the processes involved.

It is well know that the ETL is quite far away from leading products like Data Stagem Informatica and others. Currently Qliktech is working on this problem with Expressor, a powerful graphic dataflow tool. Another area is the licensing scheme, which leaves out many SMO. To remedy this and try to stop the eruption of third parties (e.g: Tableau), QlikTech launched Qlik Sense, although the future is unclear and there may be a possible merge of the two branches (Qlik Sense + QlikView). Finally QlikTech, since release 10/11, leaves the development of new graphic charts to the community with mixed results.

I have using it for the last five years, since 2010 at least.

The deployment of the dashbords, in the simplest scenario, is so easy you just drop a unique file (qvw extension) in the published folder and the solution appears into the main web page that works like an index of all solutions: the access point.

The product has great stability although in some circumstances, especially if it is low in resources or the reload process encounters some kind of dead lock while extracting the data from the DB, it could/will result in the shutdown of the service. The good news is the automatic behavior: I never saw corrupted data or unstable behavior, just restart the service / reload and all works well again.

The product is designed to scale both horizontally and vertically. Some organizatations which have servers and dashboards that handle until 30 Tb of data have had some issues that finally have been addressed by the support service of QlikTech.

Customer Service:

The customer service is provided by the local reseller and is fine. We have mainly used it to get the new releases and some support during the installation.

Technical Support:

The technical support in my country is provided by the master reseller and it looks good even when they have to pass the case to Qliktech to figure-out the problem and find a solution. In this last case it can be somewhat delayed because these cases needed to reach the top levels of the service.

I have used (and still use) Microsoft BI: SSISm SSAS and SSRS. The productivity level of QlikView is quite superior, whilst Microsoft licensing scheme is really better, specially when there are large number of users and a lot of SQL licences deployed making it (MS) much cheaper.

The initial setup was absolutely seamless and the only requirement for a successful deploy is a little training to the users, not only about how to use QlikView, but what can be done with QlikView, giving them the initial spark.

In general the vendors which I have worked with were very well qualified, although not very inclined to share information easily.

This question is hard to answer because except for a few cases its impossible to measure how the project (not the tool) improves the results of the organization. Such measures are available at the organizational level, but it is difficult to quantify the proportion of the contribution from one tool to a whole process.

The start cost is around of US $25.000 and the annual royalties are around 20% that includes customer and technical support and upgrades.

I have evaluated Tableau and Microstrategy. The first one is too basic (wonderful if you are a final user). The second one: extremely complex, just for very large organizations and large IT teams.

Think seriously about the possible population of users, how it will grow-up, and check the licensing cost and its limitations.

QlikView is based on a different technology from OLAP technology. Called AQL ™ (Associative Query Logic), this technology has been patented since 1994. If there is no need rethinking QlikView OLAP cubes, development and implementation of new elements, reconfiguring the graphical interface. Also, working with databases is much more flexible. Thus reducing the time and that the costs of implementing new analysis / reports. QlikView is easy to use, letting you easily analyze large volumes of data! Interactive graphical interface to predominantly assures unquestionable advantage over other applications. From a few clicks you can find any information in your database, no matter how "hidden" or detailed as! QlikView is a highly effective management tool, allowing a broad area of analysis. Virtually any existing information in the database the company can be valued by this application, stimulating her performance in an integrated context. • Qlikview has its own ETL engine built-in • You can analyze millions of data - QlikView is easy to use, letting you easily analyze large volumes of data! • Time to implement - Any user / manager can define its own set of analyzes • Partner Network – Qlikview has more than 1000 partners world wide • Development - Qlikview has Scripting • 64-bit in-RAM DB - Qlikview is faster than Tableau • QlikView is based on a different technology from OLAP technology. Called AQL ™ (Associative Query Logic), this technology has been patented since 1994. • Interactive graphical interface - Extremely intuitive interface (requires almost no training);

QlikView should give you just that: gather, provide access to, and analyze data and information about their company operations So, QlikView has little success by itself, so we have to go with: ERP, CRM, or some planning and estimation solutions (this would take what-if scenarios) which means other costs besides the costs of implementing QlikView This is why QlikView offers the possibility to perform what-if scenarios. • QlikView has little success by itself, so we have to go with: ERP, CRM, or some planning and estimation solutions (this would take what-if scenarios) which means other costs besides the costs of implementing QlikView • QlikView can display better analysis but it takes more skill and time to develop/design than with Tableau. • Qlikview it is stronger than Tableau for reporting only, but it requires more training and is less intuitive than Tableau • You have to employ IT specialist • It is limited by RAM, so Qlikview is not very scalable I chose QlikView specialization rather than other BI solution available on the market due to the advantages this technology offers:- Good price compared to other solutions; - Flexible licensing system (but not complicated and consists of dozens of modules that other solutions); - Very little development time; - Easy maintenance; - Ability to provide Business Intelligence Off-The-Shelf. - In QlikView, you can develop yourself analyzes you need in just minutes

I use the solution primarily for business intelligence. It’s commonly applied in the financial, human resources, and sales sectors, providing comprehensive insights across various business functions.

The platform's most valuable feature is its associative data model. It allows me to discover hidden data and gain insights that are not immediately visible.

The product's visual capabilities could be improved. The graphs and visualizations are not as aesthetic or easy to create.

I have been using QlikView since 2012. 

The product is stable. I rate the stability a ten. 

The platform is highly scalable. I have worked on projects with up to five servers to ensure scalability for large numbers of users.

I have also used Power BI. The main difference is that QlikView provides a complete solution for data extraction, transformation, and loading, whereas Power BI is primarily focused on data visualization and often requires additional tools for comprehensive data manipulation.

The initial setup is relatively easy, though there can be challenges related to licensing due to the variety of license types available. The deployment often involves a team of people, depending on the complexity of the implementation.

The platform's pricing is considered quite expensive, particularly given the dollar-based pricing.

The associative data model in QlikView uses color-coded indicators (white, green, and gray) to show data associations. This helps me identify how data points relate to one another and discover hidden insights.

I rate it an eight. 

So the primary use case of QlikView, I have worked with financial maintenence.

You can do a lot of things at the back end which are not possible in the other solutions in the market.

Tools that can be improved are:

• Visualization charts
• Pricing
• UI transparency

One to three years.

The Qlikview is quite stable in comparison to other solutions.

It is a very good scalable solution. 

The tech support is strong. The logs of the documents are helpful. 

I have some prior experience with Power BI and Qlik Sense.

The initial setup is not very complex, it is on a moderate level. If others compare it to other BI tools, they may find it complex. But it was not a problem for us.

The pricing is too high compared to the other solutions on the market.

There are features of QlikView that are not available with Power BI or Tableau. There are activities on the back end that work better in QlikView.

You can do a lot of things at the back end that you cannot do with other competitive solutions.

E-T-L, The Extract, Transform, and Loading capabilities of QlikView make it a highly sophisticated self-service business intelligence tool for developers and analysts who desire much more advanced handling of dirty or unconsolidated data. QlikView scripting language has numerous transformation functions.

As a consultant for my organization using Qlik to design management dashboards, analysis and ad-hoc reports, I have seen the way it has helped many of our clients get the desired reports and analysis for their stakeholders and top directors which would normally take time and more effort to get.

The user interface and ease of use takes a bit of a learning curve to pick up. There is no drag and drop functionality at the development stage unlike its competitors. Maybe QlikSense could handle that area.

We have been using the solution for five years.

We haven't yet encountered any issues with stability.

QlikView is a memory intensive application and does sometimes start to weigh on your PC resources. Also you would need to learn some development tricks to manage unnecessary time wasting when loading large database sources, like the use of QVD – QlikView proprietary data format - for faster and efficient loading times.

The Qlik community is very vibrant and you find or get answers to most issues started or any other areas.

We did not use a solution previously.

The initial setup is pretty straightforward for personal use, except when you are looking at deploying the QlikView server which will entail some configuration instructed during the installation process.

QlikView pricing and licensing is on the high side for a small sized company, but it's competitive among its peers.

As a consultant in the area of business intelligence and data analytics I have had to personally evaluate QlikView with other self-service BI tools such as Tableau, Power BI and MicroStrategy.

Invest in the memory and RAM of your PC or server you intend to use for QlikView. Ensure you have all the necessary resources and connectors installed for proprietary databases.