QlikView Reviews

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.

It's essentially building dashboards for BI. So, the primary use case is back to the reports, particularly dashboards.

One of the good thing is that you can integrate different data source technologies. So you can model your environment without having any of our views running. And I see that our tool would essentially have its own programming language. So that's how you can customize a lot of things.

I'm not like a lot of people who are into AI, especially when it comes to making queries. I don't really remember if QlikView has this feature, the one where you write up a question about the data in human language, and they just bring up a quick analysis from it.

I'm not sure if this feature exists. But if it doesn't, it should be something they consider adding. I believe assisting users with quick building using natural language queries is not as simple as just making a regular query.

I like the idea of using human language queries. That would be a plus, really.

QlikView should improve the integration with scripting. It has its own scripting language for building the underlying data layer. Sometimes, dealing with complex reports requires more effort, and that could be really improved.

I have been using this solution for four years. 

It's quite stable. The problems I've faced were mostly related to data issues rather than the solution itself. So I would rate it a nine out of ten in terms of stability.

I haven't encountered issues with scalability personally.

I am satisfied with the support. 

Neutral

I would rate my experience with the initial setup a six out of ten, where one being difficult and ten being easy.

The duration for deployment varies depending on the project's complexity. For some projects, it could take a few weeks, especially when dealing with large reports and multiple dashboards. But there were also cases where it took only a few days.

Usually, there were three or four people involved in the deployment process.

I've worked with Tableau, and they were different at the beginning, Tableau being at an advantage, but now they're very similar. Both QlikView and Tableau have their strengths and weaknesses. Tableau was a bit easier for creating storytelling, but I don't have any issues with QlikView. Additionally, I'm not a big fan of Microsoft Power BI, but I haven't tried it out, really. It has some interesting features, but sometimes it feels a bit too verbose.

I would recommend proper planning, especially because you have to build the underlying model that will support your dashboard. This is very important.

Overall, I would rate the solution an eight out of ten. To achieve a ten, they should improve the integration with scripting. Sometimes, dealing with complex reports requires more effort, and that could be really improved.

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.

Positive

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. 

We've got a third-party provider that consumes our data, and they have QlikView experts or QlikSense experts who visualize and create business-type reporting and insights for our other business users to use.

We do operations and monthly reporting via QlikView. We usually have various types of business use cases for different business units, and it is used for all those reports. We create reports for each of the business units based on their requirements. Our users can log onto the portal and prepare all their reports in one place.

QlikView is old, and we are now moving towards a Power BI environment. We are moving all our reporting over to Power BI.

It is useful to use a tool like this to have a view of data at a point in time. You can extract and create little data sets that you can store, and then over time, you can have a view for tracking changes. Especially when you work with a relational database or a database that's a production database, the data is dynamic, but if you use QlikView, you can take a snapshot of different datasets. In your own time, you can then get insights and report, build, analyze, and draw whatever you need from the data, which is quite useful. So, it is easy to create a data set of specific fields or variables that you need. You create the snapshot, and it then basically stores that into its own little file that you can build over time. 

It is really old. We are moving towards converting everything into a Power BI environment. We want to have a self-service type of BI environment where different levels of users in organizations can log onto a portal and retrieve the data they need or get the necessary insights for decision-making that's important for them or their business unit. They have built a new version of QlikView called QlikSense, which probably competes with newer BI tools, such as Power BI, but they are far behind. That's why we are moving towards a newer tool that's easier to use and has more visualizations to represent the data. QlikView is very old, and there are more modern tools that work.

It is expensive. Its licensing can be improved because the tool is old. If they still want people to use it a lot, they should substitute it for a newer, better BI tool. The price should change for what you get. They can have a cloud version for it, but I guess they have created QlikSense to have a cloud version or platform available so that people basically go from QlikView to QlikSense.

There is a learning curve. It is not for first-time users working with data. It has got its own little syntax to create usable datasets, codes, schedules, etc. So, there is quite a learning curve to learn the syntax to use the tool, but if you build expertise in it, it is nice to use.

I have been using this solution for about 10 years.

It is stable. It is resource-intensive, but it works. It is not bad; it is just old in terms of functionality.

It is resource-intensive. So, it is not easy to scale. In my organization, we have about 50 to 100 users who are using the actual QlikView portal to draw reports. We have 5 to 10 users who are building and creating reports.

I have not really used their support. We have experts in QlikView. If we struggle with something, we've got QlikView consultants, and they have expertise. Every now and then, we do contact them if we're having issues with QlikView.

It is of medium complexity. It is not easy, and it is also not difficult. It takes a little bit of time to get the hang of it. If you have some kind of experience in working with these types of setups, it is quite easy to learn.

It has an annual license. It is expensive as compared to other competitive tools that do more for less. In South African rands, we pay about 100,000 to 200,000 a year.

I would recommend QlikView for a small business with very specific data needs. QlikView makes sense for small businesses with a very specific data environment where data is controlled, and there are one or two people requiring the data or reports. For anything bigger than that, there are other more modern tools that you can use at a lesser cost.

I would rate it a five out of ten because there is quite a learning curve for using the tool, and it has been falling behind other tools.