QlikView Reviews

The most valuable features of the product are its in-memory and ETL capabilities, especially the set analysis function.

We developed in a couple of days an application based on a timesheet application, in order to have a real-time vision of what we do in IT service. Before, there wasn't any system except some Excel manual spreadsheets.

We developed a QlikView prototype based on sales data to give easy and visual access to the data. It took minutes to be loaded, compared to the existing system of traditional cubes that required hours to be loaded... to give what? Reports without any interactivity.

QlikView should improve its front-end design and import the Qlik Sense design within.

I have been using it for two years.

We used the Nprinting extension. A great toot to create PDF reports, etc... However, the tool is not stable; installation was difficult before being able to use it.

I rate the level of customer service and technical support 8/10, efficient.

I previously used IBM Cognos, Tableau, MS, SAP BO... Personally, QlikView is the best when you talk about fast delivery and visualisation.

Initial setup was straightforward: half a day and your QlikView server is up and running.

I implemented it in-house, but I had QlikView experience.

QlikView is like a race boat, compared to other vendors who are king of Queen Elizabeth. ROI is never easy to measure but at the very least, you will definitely deliver something with added value to your customers within weeks.

Consider the ETL capabilites of the tool, not only the visualisation. And, of course, the performance!

Once you select any data on the dashboard, QlikView highlights the unavailable data in grey in order to show to users that those combinations don’t exist or aren’t possible.

Filters are not local. Once you filter something, the standard is to apply the filter to all tabs available in the dashboard.

They used to manage the business data through spreadsheets, now they have an automates process and a stable solution. It reduced to zero the time to prepare the data, avoiding operational issues and allowing them to put all the focus on business analysis.

Qlikview should have a connector or a specific product to allow people outside of the company or that don’t have a license to read/use the application (a kind of reader license). At least something really cheaper or free.

I have used QlikView for three years.

I have not yet encountered any issues with deployment, stability or scalability.

I rate technical support 8/10.

The time or effort to develop new stuff in QlikView is lower than other traditional tools as MicroStrategy, Cognos, etc. Besides that, we are changing our approach to a self-service BI.

The initial setup was straightforward. QlikView allows you to install it on regular desktops with 8 GB memory. After some time, we migrated QlikView to a server with 64 GB, due to the number of users and the amount of applications developed.

We implemented/developed with an in-house approach.

I would advise that the first implementation should be done through a vendor team in order to have better standards/best practices applied from the beginning. It would speed up the learning curve.

For this specific case, we didn’t calculate or estimate the ROI. Comparing QlikView to Tableau, I think that Tableau has a more attractive pricing/licensing approach than QlikView. I would recommend studying it before starting to acquire new licenses in QlikView due to the model of sales (Named Call and Document Call). The cost of new licenses could increase faster if you don’t have in mind the proper usage.

Qlikview has a huge community in the internet with a lot of examples, online course, etc. It will help a lot to test by yourself. I would recommend providing a POC among the tools to identify which of them would fulfill your needs better.

• In-memory performance – It allows slicing and dicing of a huge volume of data in the dashboard very fast if designed optimally.
• Scripting – It provides a flexible data-preparation layer, along with the ability for data integration from multiple data sources. This enables creating a reporting data model inside QlikView from a transactional system without impacting the performance of the transactional system, if designed correctly.

Overall, it enabled connecting the entire spectrum of data into a single dashboard in:

• Finance – connecting sub-ledger txn details all the way to GL
• Supply Chain

• Self-service capability is very limited, though it has been improved in QlikSense. However, it will require an additional license & server to set it up.
• Dashboard capabilities and features are not on par with Tableau, though the same has been attempted in QlikSense. However, Tableau still has better dashboard features.
• Real-time analysis with live connection (direct discovery) is very limited.
• The current version is missing a variety of connectors and they need to be procured separately.
• Not adaptive to display across various screen resolutions

I have used this solution for two years.

Initially, there was an issue with LDAP and SSO integration (a compatibility issue with an earlier version of SiteMinder).

Initial setup was non-clustered and we encountered performance issues. It resolved once we moved to better infrastructure in a clustered environment of QlikView.

Technical support is very geographically oriented, but isn’t truly 24X7.

Initial setup was not intuitive, but straightforward for a Qlik admin expert.

A vendor team implemented the solution.

I evaluated Tableau. However, we selected Qlikview because:

• Tableau’s current recommendation is to build dashboards directly on top of the reporting DB (for example – data mart or consumption layer) to avoid doing complex logic or transformation inside the tool and using a hybrid approach of live connection and extract. Tableau is currently not an extract-heavy tool. However, with the recent HyPer acquisition, we are expecting some changes.
• Incremental loading (updates and deletes) inside Tableau is a challenge, which can be achieved very easily in QlikView.
• Limitation in Tableau on # of columns and rows in table view

Evaluate visualization tools based on your organization need and appetite to spend on BI technologies overall (DB, etc.)

SQL scripting, as it provides me the fastest way to pull data into the system, since I’m more on the technical side.

It has made our processes for collecting and presenting data easier, especially with regard to old spreadsheet mentalities.

Their marketing department is heavy-handed, more so than it really needs to be. This can turn companies off when they get too aggressive. Their pricing structure doesn’t match their aggressiveness either, costing an end user $1500 for a web-based license.

I have been using QlikView for about 11 months.

Their set criteria is a mystery of legends. I still, after a year, need to pull up a wizard to type up a set expression. It’s not intuitive at all.

Technical support is very good, with an exceptional user base. I’m largely self-taught on Qlik because of their community and the breadth of their support on-line.

I previously used Microsoft BI tools, but as a company we were too far behind the curve to take advantage of their latest technology in the BI space. Upgrading to Office 2016 is not something a Fortune 500 company is going to do overnight.

The desktop component was straightforward. I didn’t set up the server component, so I can’t speak to the publishing.

An in-house team performed the implementation.

No definitive ROI, but an enterprise license would go a long way towards adaptability and acceptance.

QlikView and QlikSense are powerful tools that require IT and BI expertise to take full advantage of. True BI utilization is not just dragging fields and creating graphs. It requires deep knowledge of data utilization and visualization. Qlik can provide that, BUT at the cost of additional IT or BI expertise.

• Flexibility
• Agile development
• Intuitive
• Very good performance
• Excellent user groups

We use QlikView to create department dashboards. We can create powerful dashboards with useful analysis in a few days.

I think its visualization has room for improvement, and I know Qlik Sense has better visualization.

I have used it for two years.

It's difficult to manage big and complex data models, but the reason is that there isn't a semantic layer in Qlikview, but not having a semantic layer is a good point in other aspects, like agile development.

Excellent, very good and active community.

I have used Business Objects and Microstrategy. QlikView is a different tool. It has advantages and disadvantages compared to Business Objects or Microstrategy. The main advantages are flexibility and agile development.

It was straightforward.

We haven't calculated the ROI yet.

I think the pricing is really competitive.

QlikView is an excellent reporting and data discovery tool. I have used it on a departmental scale, but not on a corporate level so I don't know how it will behave on that level.

• Data discovery
• Set analysis
• Adhoc reporting
• Drill down options
• Flexibility
• In-Memory technology
• Quick learning curve
• Easy to deploy

The product enables top management with better decision making if utilized properly.

QlikView should not loose its original flavour. They should stop trying to emulate other BI products and mould their own product.

I'm using the QlikView local client.

It is best suited for Dashboarding, Analysis and Reporting. Do not try to re-implement everything from a previous BI product if you had one. Ensure that the QlikView features & functionality are properly utilized to get the best out of it.

• Ease of use
• NPrinting
• Visually good diagrams
• Integration with almost all databases

• Associating links

We have used this product for a number of different clients, and most of them liked the software and all the rich features it bring with it. The amount of data it displays on the dashboard with such a ease, helps users to always get the results in desirable time limit.

They are coming up with a lot of improvements. However, the version control is not one of them, and it's not straightforward.

We have had no issues with the deployment.

There have been no stability issues.

We've had no issues with scaling it for our needs.

There is a number of criteria you have to see before you start implementing the product, as you compare Qlikview with other tools such as Tableau. You make sure that you check the cost, ease of use, differnt ways to displaying the information etc.

1. QlikView Scripting - Takes some time to learn, but it is very powerful. Not as a total ETL replacement tool necessarily, but as a supplement to load and join data sources, perform additional transformations, add supplemental inline tables, and even at times, output a final .txt/.csv for consumption by other tools (even Tableau!). I've combined as many as a half dozen data sources including data from multiple SQL Data Marts, Teradata Data Marts,Source System DBs, XLS, CSV, and Google Big Query.

2. Design Flexibility - While other products may do drag and drop, ad-hoc reporting analytics better. (Including Tableau, and Qlik's new product QlikSense) I've not come across one that better supports the creation of a polished, packaged, custom dashboard, that supports what I'd consider "guided exploration", and best meets the needs of our user base. The customization can be taken even further through in-house built, or borrowed, extensions (e.g. Custom D3 Visualizations).

We have gradually reduced laborious manual reporting in Business Units and "spreadmarts". We now have some executive using QV dashboards in weekly review meetings, in place of spreadsheets and PowerPoints. While it does take some time and IT involvement to initially develop and deploy a solution, the payback is immediate. In one particular case we were able to eliminate a days worth of manual work with a QlikView solution that required a few days of development effort. We also previously had no way for end users to routinely and easily analyze larger (100 Million+ rows) data sets, which now can be done through QlikView.

No out of the box mapping capabilities (Extensions/Plugins available).

No auto-scale for different display resolutions/dimensions, but the trade-off here is the much greater design flexibility than one gets with a Grid based product.

Would like to see a few more visualizations available out of the box (e..g Bullet Graph)

Very rudimentary report creation and PDF capabilities No scheduling or distribution without Publisher product.

2 1/2 years

None.

None thus far, but have a relatively small scale implementation (30-40 Users to date), on a single server (196GB RAM, 15 Core). Our largest data sets are in the 100-200 Million rows. Dashboards deployed to the server perform very well, but working with data sets that large locally (on QlikView desktop) may start to lag, depending on your hardware. Being a in-memory tool, desktops and laptops should have at least 8GB RAM, though even more is preferable if working with very large data sets.

Customer service was/is excellent.

Our need for technical support has been minimal, but when needed it has been great. The overall Qlik Community is phenomenal. Many problems can be resolved through the community channel. Users often provide example files one can reference or reverse engineer.

Previously used an older Domo product (Centerview). The product was no longer supported. It was very flexible, but also very labor intensive. Data had to be fully prepared outside of the tool ,and every interaction had to be defined. Development time was weeks vs days in QlikView.

Currently also using Tableau, depending on the particular use case.

Straightforward setup. Connected to Active Directory to manage users.

In-house with some set up assistance provided by the Qlik sales support team.

Server is Apprx $35K initial cost, plus 20% annual maintenance/support cost

User licenses are $350 or $1500 depending on license type(plus 20% annual maintenance/support). This can get costly if you have a very large user base.

Several. If interested see my post http://www.itcentralstation.com/articles/i-evaluat...

I would never propose QlikView, or any other single tool, as THE definitive data visualization and dashboard tool for every organization, but it did best meet our particular needs. Organizations with more data-savvy, self-sufficient business users may find a product like Tableau, or Qlik's other product, QlikSense, to be a better option.