QlikView Reviews

We employ it as both an ETL tool and a visualization and analytics platform. It provides interactive visualizations and business intelligence capabilities.

The most valuable aspect is its extensive library on Microsoft, providing a robust framework for implementation.

Enhancing user-friendliness would be highly beneficial. It could become even more remarkable if it were available in the cloud, retaining the core functionality of its engine and offering the same seamless user experience. There could be enhancements to the Qlik Management Console. Specifically, the user interface and user experience could be refined to better manage execution sequences. Currently, there might be overlaps between executions and deployments without clear alerts or notifications. This lack of alerts could lead to issues like concurrent job executions causing system downtime or memory constraints. Improving the sequencing of deployments and incorporating smart notifications would significantly enhance the overall process.

I have been working with it for ten years.

I would rate its stability capabilities eight out of ten.

Scalability is paramount, given that it often constitutes a significant cost for companies. Initially designed for around thirty users, our server infrastructure has undergone notable expansion over the past two years. We've exceeded hundreds of users, particularly with large clients like the government, who now boast a user count surpassing a hundred. I would rate it seven out of ten.

The community around it is robust, and I am extremely pleased with the level of support they provide. I would rate it ten out of ten.

Before adopting QlikView, our team previously utilized SAP's Business Objects for scalable enterprise solutions. Tableau was also present in the market at that time, predating QlikView's emergence. I found Tableau to have an element of complacency. However, upon transitioning to QlikView, I perceived it as a superior and more dynamic solution.

The initial setup was quite straightforward. I would rate it ten out of ten.

Getting the dashboard up and running typically doesn't take much time.

It's reasonably priced and falls on the more affordable side. The annual cost for this, including server licenses, was approximately thirty to thirty-five thousand dollars. I would rate it five out of ten.

Overall, I would rate it ten out of ten.

Within our customer base, we have manufacturing companies that produce goods like machine pumps, and these firms rely on QlikView for their production processes.

Our clients are looking for a migration process that's as trouble-free as possible, and Qlik Sense is doing well in areas such as database connections and integration, including in SaaS environments where QlikView is still a valuable option. It excels in supporting database connections and various database types.

They should offer the capability to directly access data from SaaS environments, as it would simplify the migration process, and while it may seem like a minor enhancement, it would be beneficial to our clients. Some clients have requested a hybrid environment where both QlikView and Qlik Sense can work together effectively during the initial stages of migration, so that would be a good feature to add.

I have almost twenty years of experience with it.

I would rate its stability capabilities nine out of ten.

It offers excellent scalability abilities. I would rate it ten out of ten.

I would rate their technical support eight out of ten.

Positive

The initial setup was straightforward. I would rate it nine out of ten.

The deployment process involves linking various units and requires careful project planning, including determining the necessary components, deployment strategies, and the overall timeline for the entire process. The duration can vary significantly, typically spanning from one week to several months, contingent on factors like the complexity of the customer's needs and any difficulties encountered during the migration or the implementation process.

It is quite expensive, rating at around nine out of ten on a cost scale. This is mainly due to the requirement for a dedicated ClickView infrastructure as the sole SQL solution. We are primarily using perpetual licenses at the moment, and it's essential to note that we currently have just one SQL solution, which comprises one two-cluster. This incurs a cost of €21,375 for the solution in the current setup.

It is highly valued by our customers as a powerful tool, but it must continue evolving and staying relevant. Overall, I would rate it nine out of ten.

We use QlikView in combination with Salesforce. It provides convenient business analytics and sales tracking. QlikView provides access to data offline. I use this option most often since I can get important information wherever and whenever I need it. 

QlikView is quite intuitive. Its interface looks like Excel. It's cool due to the fact that it provides convenient filtering options.

QlikView has helped improve several aspects of our organization. For example, it provides us with a deeper understanding of our sales and customer service processes. 

Thanks to QlikView, our sales teams now have access to real-time information, enabling them to prioritize leads, identify bottlenecks, and close deals more efficiently. 

The most valuable features of QlikView for our organization have been its robust data analysis and visualization capabilities. In addition, the integration with Salesforce has helped us gain access to crucial sales data in real-time. Salesforce is a reasonable price compared to other applications. 

While QlikView is a powerful tool, there are areas where it could be improved. There is a lack of static PDF report generation and automatic resizing of the dashboard to fit the device, for example. 

Also, scripting can be a bit difficult if you don't have the necessary knowledge, so this app may not be suitable for everyone. 

I've used the solution for about six months.

I use different apps with Salesforce. They include Tableau, Conga Grid, and Rollup Helper. I haven't switched. I'm researching the best solution.

I evaluated Tableau, Conga Grid, and Rollup Helper.

The most valuable feature of QlikView is the integration with other third-party tools. 

The solution should be mobile-responsive. It should also include drag-and-drop and slice-and-dice features. 

I have been working with the solution for eight to ten years. 

I rate the solution's stability a ten out of ten. 

I rate QlikView's scalability a seven out of ten. My company has around 500 users for it. 

I provide technical support to my customers. 

I rate QlikView's installation a ten out of ten. It was very easy. Deployment depends on the project and its scope. It can take around one week to three months to complete. You need one resource to handle the maintenance and deployment. 

I rate QlikView's pricing a five out of ten. 

I rate the solution a seven out of ten. 

The feature I found valuable in the solution is the power of VPN and the power of representation of data. Also, the speed of performance is a valuable feature of the tool.

There are a couple of things right now to consider since QlikView is going to be out of the market. Instead, Qlik Sense will be the new platform. Right now, QlikView is switching up. So there are some enhancements in Qlik Sense required.

Though the initial setup phase is simple, when it comes to the integration with the custom systems, the configuration and the compatibility sometimes take some more time. The aforementioned area can be considered as room for improvement.

I have been using QlikView for almost ten years. Also, I am using the solution's latest version. My company has a partnership with Qlik.

Stability-wise, I rate the solution an eight out of ten.

Scalability-wise, I rate the solution a seven out of ten.

Considering one of my largest customers, I think that 4,600 users are using the product.

I rate the support an eight out of ten.

Positive

On a scale of one to ten, where one is difficult, and ten is easy, I rate the setup phase an eight.

The solution is deployed on the cloud and on-prem environments.

The deployment process is an activity consisting of a few hours.

For the initial setup, one person was able to install and configure everything. With respect to the development, it depends upon the customer-to-customer requirement to requirement complexity of a business. But initial setup and configuration have been done by only a single person.

On a scale of one to ten, where one being low price and ten being high price, I rate pricing a four.

We evaluated a couple of other platforms before choosing QlikView. So the other ones were Tableau and Power BI.

Speaking about the main differences, along with the pros and cons between these products, I would say that I think the capability of handling a large volume of data is one of the bigger challenges. Also, ETL capabilities are limited with Tableau and Power BI, whereas QlikView is able to handle a large volume of data, and it also has a stronger ETL update.

QlikView is one of the strongest tools, I would say. Also, it has a very vast capability to process the data. So, definitely, one who has a large volume of data should go with QlikView as an option. Currently, as I mentioned, QlikView is upgrading its product suite, and they are adding many new tools with different features. So I think it is one of the best options if you are thinking of an end-to-end data analytics platform.

I rate the overall product a nine out of ten.

We use the product for data analysis, sales operations, and sales demand planning and forecasting.

QlikView's UI could be more user-friendly. At present, I encounter difficulties while writing complex queries on the UI. It doesn't support the query button as well.

We have been using QlikView for three years.

I haven't come across any stability issues for the product. However, a particular error keeps surfacing whenever the threshold for the number of onboarded users crosses the limit.

I rate the stability a five out of ten.

We have 30 QlikView users in our organization.

The technical support services are good. However, they could prioritize critical issues. This particular area needs improvement.

Neutral

We use SAP Crystal Reports.

I rate the initial setup process a seven out of ten. It took half a day to complete product testing and implementation. We receive support services from the vendor for maintenance.

QlikView is more expensive than SAP Crystal Reports. It could be improved. I rate the pricing a five out of ten.

We extensively use QlikView for data visualization and analysis in our organization. It connects to ETW and Data Mart, helping financial executives visualize the data. It has user-friendly data visualization features, supporting our decision-making process with its business intelligence capabilities.

The integration between Qlik Sense and QlikView has proven most valuable to our business. Its speed and efficiency in processing large datasets proved moderately beneficial for our organization, with some performance challenges arising during complex joint operations.

It is a good tool to use and has efficient data visualization features. I rate it a seven out of ten.

We use it for obtaining incremental data updates and QVD file downloads.

It enables us to configure various elements, such as dashboard settings, including factors like color schemes and other customization parameters.

There's room for improvement in the area of management's handling of concerns. They should integrate Qlik analytics and seamlessly transition users from QlikView to Qlik Sense.

I have been working with it for two years now.

I would rate its stability capabilities nine out of ten.

I found Qlik Sense to be more scalable than QlikView.

During the server migration process, I seek technical support for guidance and consultation.

Positive

Prior to using QlikView, we employed Sub-Business Objects. Qlik is more prominent for creating interactive dashboards and visualizing dynamic numerical data related to benefits, and allows for the download of data.

The initial setup was easy.

The pricing is moderate, in the medium price range.

Overall, I would rate it nine out of ten.

For now, our use cases are mostly the common analytic tools. I'm not involved with any AI or machine learning solutions, only dashboards and reporting.

The common analytics tools of the solution are valuable. 

There is room for improvement in terms of scalability. Because it depends on the use case and customer requirements. 

If QlikView can't handle the scale, I usually look to the data lake or data warehouse for solutions. My experience is that for self-service BI, users often request low code tools, which wouldn't be suitable for the QlikView front-end due to performance limitations.

I have been using the solution for almost ten years now.

It is a stable product. 

Scalability really depends on the size of your data and QlikView server architecture. For the biggest data sets, it could become an issue at some point.

We haven't actually used technical support for Qlik. We've always been able to solve problems ourselves.

I don't recommend any specific BI front-end because customers usually suggest the tools themselves. I focus on the data lake and data warehouse. As long as the chosen tool is QlikView, Tableau, or Power BI, I don't see much difference. So, I always recommend those three.

We can handle all three tools, so it's more about understanding the customer's specific needs and suggesting the best fit.

We handle most of the difficulty in the data warehouse, so the front end is relatively simple. We just use the common features. 

My customers are mostly in government and banking, and they haven't had issues with QlikView pricing.

My recommendation depends upon the Gartner's recommendations. Currently, the top BI tools are Power BI, QlikView, and Tableau.

So, it's pretty good. I'd rate it an eight out of ten. 

In my company, we use QlikView for dashboards. With QlikView, our company tries to ensure that we capture all operational items in the dashboard so that the management can take action based on that.

I think the main benefit of QlikView is that it is an incredibly powerful tool, as it can handle millions and millions of rows.

QlikView certainly lacks in its ability to share visualizations or create visualizations easily. QlikView is a powerful tool but has shortcomings when compared to the visualization capability provided by Qlik Sense or Power BI.

From my perspective, I understand that since QlikView is an older product, it can be simply left as it is, and users can move to Qlik Sense, which provides a much stronger visualization.

If QlikView decides that its visualization part should be just like Qlik Sense or Power BI, then I would say it would be too much to capture in one or two phrases, considering that it is overall much easier to create visually good-looking dashboards and also something like a geographical map which is not possible in to get in QlikView currently.

I have been using QlikView for years. I am a user of the solution.

I am happy with QlikView's stability. Stability-wise, I rate the solution an eight out of ten.

QlikView is a scalable solution that multiple users can easily use.

My company has 20 to 50 users of the solution.

QlikView has a lot of resellers, and my company has been in touch with one of QlikView's resellers. It is QlikView's reseller and not the support from QlikView that my company contacts for help. I rate the technical support a seven out of ten.

Neutral

The solution is deployed on an on-premises model.

QlikView is a reasonably priced solution.

I would suggest others to QlikView and go for Qlik Sense. Qlik Sense is a tool that is as powerful as QlikView with better visualization capabilities. I would not recommend anyone to use the older QlikView, but I would recommend anyone to move to Qlik Sense.

I rate the overall tool an eight out of ten.

I'm using the product for traffic purposes, leads, and some users. It's about the approval ratio. I'm using data to see what I want to see and based on this, I'm creating some reports for myself and management. Whatever I want to see, whenever I want to look something up, I can do so with this product.  

If we have an FTD, we can see when this FTD came in. This is very, very important for me and for our team to see how the actual FTD came in and when, as, for our department, we are building campaigns for traffic. If we have an FTD that registers today and deposits today, this is different than another scenario where we have when leads from last year that are deposited today. The faster I can see this, the more helpful it is. This is a key feature for me.

It's easy to use in terms of navigation. Once you open it up, you see everything that you can do. You can see what filters you have to choose from right at the beginning, on the first page.

Sometimes the filters are disappearing, and I'm not sure why this is happening. It might be when it's refreshing or updating. I'm not sure. For example, maybe when I'm doing a report and it's refreshing, I can see that all my filters are gone and I need to start again from the beginning. This is the main issue for me.

I've used the solution for one year and six months. 

For the past year and six months, it has been very stable. The numbers are correct as far as I can see. Based on this, reports are created. We haven't had an issue. It's reliable. 

We have 30 or 40 people using the solution currently.

I'm not sure of total scalability, however, based on the scalability of the data, of course, it has a lot of scalability available since we have thousands of FTD leads. We need scalability. So far, we haven't had a problem achieving it. 

That said, if the solution can scale according to the number of users, I'm unsure.

As of now, project coordinators and the business intelligence team are using it. 

I don't have any communication with technical support.

I'm using Qlik Sense as well. It's something very similar. It's just some different places that you're going to have. You're going to find some different filters, however, at the end of the day, it's very similar.

I didn't handle the initial setup and I'm just the one user. 

I'm an end-user of the product.

I'm not sure which version of the solution we're using at this time. 

My advice to everyone that is using QlikView that's a beginner is to check every page that it has. When I started using it, after one or two months, I found a lot of pages that were very important for the company. If I knew they were there from the beginning, I would have checked those pages instead of using only one or two things. Every page has very important info.

I'd rate the solution at an eight out of ten.