QlikView Reviews

Memory data management, quick analysis and reporting.

We can collect and analyze information; until now information was spread across different sites, databases and spread sheets, managed by people belonging to different organizations. Now reports are available in short time in a single source.

Graphic User Interface, the product could be improved by a smarter, more intuitive and friendly interface for graphs or reports.

2 months.

No issues with deployment. 

No problems with stability. 

Yes, we had issues with scalability. 

Not enough data to give an opinion. 

Very easy setup.

We have not yet quoted a ROI, we expect a valuable saving of time and resource by cutting manual reporting, better decision making processes, and on time strategic management alignment.

We are in early evaluation phase.

Its easy and fast to build dashboards.

One year

Sometimes the product final (look & feel) is different from the desktoop tool and the web server.

Its a product very stable

No

4 out of 5.

4 out of 5.

Microstrategy. We changed because Qlikview is faster to build a dashboard than Microstrategy.

Vendor team

Good expertise

Tableau

We use it for analytics and for insight as well, what we call our standard reports, tabular reports. But mainly, to create a dashboard and analytic views.

The in-memory feature gives us better insight. It's also easy to drill down into the information and select information. Of course, it has the typical functionalities. For example, when I select something I can know its opposite.

For me, it is important to have a mix, what is the "view" and what is the "sense", Qlik Sense. They have two tools, but for me it is important to have only one tool that combines the functions we have from one side and the other side. One application.

Also, they have not come out with new functions for QlikView. Qlik Sense has evolved but not QlikView.

Another problem is the printing. It is not a solution that comes with QlikView. I believe we had to buy it. It is not integrated. It is not the easiest to manage. It is not as easy as it could be.

It is stable.

Right now, we are facing a challenge concerning the capacity, or balancing the use of the servers. In the end, we expect to have a good resolution.

We were using a different solution and we still use a part of that solution, SAP. SAP Business Warehouse and SAP BusinessObjects. We faced a lot of problems in the migration between BusinessObjects and BW. In the past, BusinessObjects was a separate company that was bought by SAP, so we had a lot of problems in terms of integration. It was not possible to pursue these solutions with so many problems. We could not deliver solutions with that platform, so we went to the market to see which other solutions there were for creating the output: the reporting, the analytic views, the dashboard creation. 

The most important criteria when it comes to selecting a vendor are the vendor's position in the market, and the solution itself. If we are going to change from one supplier to another supplier, we must have confidence in that new supplier. Other factors are the functionality of the solution and the cost of implementing the solution.

It's not complex.

We did a comparison between Microsoft Power BI and QlikView, and we decided on Qlik. That was five years ago.

I rate QlikView at eight out of 10. Compared with the SAP portfolio, in terms of administration, I think it lacks features.

My advice, today, is you must look at the others, like Tableau or Microsoft, to compare. Everyone has their own objectives, what they want to get from a tool, so compare and see which ones respond to the requirements.

Easy to implement.

Easy user adoption.

Data Science.

For eight years.

Not often.

I don’t think scalability is applicable to QlikView.

Yes, it was straightforward.

Use QlikView for business, and Qlik Sense for BI developers.

Because it provides data discovery along with BI solution design, it has a distinct advantage for data analysts.

Associative Experience is also valuable.

The solution can be implemented quickly (normally within three months) with a low implementation cost.

I have been using QlikView for the last four years & am currently working on version 11.2 SR14.

Deployment of the QlikView solution is more or less smooth & simple compared to other BI solutions.

Scalability is directly proportional to RAM size & the number of concurrent users accessing the solutions. We didn't see major stability-related issues post-deployment.

The Qlik support team is very active & responsive. Issues are mostly resolved on time.

I hadn’t used any other BI tool, but our organization migrated to QlikView from SAP BO because of its associative experience & quick deployment time.

Initial setup was complex with respect to building the same project environment for a different business domain.

Implementation was done directly by Qlik, which made sure the best design methodologies were kept in place.

ROI is much better compared to BO because deployment time & cost are both reduced.

Qlik’s pricing / licensing policy is fair enough.

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.

Ease of use, visualization, intuitive, the Qlik method of ETL, Qlik Sense

Analysis in real time, predictive analytics, reporting

Server performance. Reloading of data sometimes weigh down the server's performance.

1 year

No issues with deployment.

Slight issues with stability.

No issues with scalability.

8/10

8/10

SAP BusinessObjects. Change in business requirements.

Vendor - 7/10.

Yes. SAP BOBJ

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.