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.

• Ease of use
• High custom development potential
• Adaptability

We are now getting coordinated management areas, which were practically delinked until now.

• More support through contextual menus
• Adapting to the new Qlik Sense (HTML 5) environment

I have used it for eight months.

I encountered difficulties managing computer RAM.

Technical support is 8/10.

Initial setup was straightforward.

We implemented QlikView independently without difficulty. We needed support for installing Qlik Server.

We are at a too-early stage of implementation to evaluate this, but we anticipate difficulties in expanding its use due to the high cost of licenses.

We use QlikView and Oracle BI, but the productivity-to-cost ratio is much higher with QlikView.

You need to assess carefully the choice between QlikView and Qlik Sense. We do not understand too well the coexistence of two products with the same function.

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.