QlikView Reviews

The strongest characteristics of the product are its ease of use and its data discovery and exploration capabilities:

• Ease of use, as it is very intuitive, as long as its back end data model is well designed, providing its end users with a high level of autonomy and the developers with a very intuitive and complete set of tools.
• Data discovery and exploration, thanks to its in-memory data association capabilities that provide a fast and easy way to relate and explore data.

As a consultant, QlikView has helped me deliver high-value BI solutions to my customers, consistently exceeding their expectations and creating new opportunities for my firm.

It could be more mobile friendly, as some of its features don’t work properly on mobile devices or do not provide the best user experience to our customers who would like to extend their access to data. A Cortana/Siri-like feature or advanced analytical capabilities for users with advanced scripting and statistical skills would also extend its usage in the organizations where I operate.

I have been working with QlikView for about 4 years.

I still find some fine tuning issues when scaling up in concurrent usage or data volumes.

Strong customer service, not as strong on the technical part, and the community is still a bit underdeveloped.

I’ve also worked with other main market solutions like Microsoft, or Tableau, but over the last few years, QlikView has evolved considerably, especially when they completed it’s offering with Qlik Sense 2. Although it is not as versatile as the Microsoft solutions, it is stronger in ease of use and development when compared to Power BI for example. It’s licensing costs when compared to Tableau are also a differentiating factor.

It was extremely simple and straightforward to implement.

We do our own implementations without the need for a high level of involvement from the QlikTech vendor team. Our main advice is that a good understanding of how tabular models work when designing the data model, and a good understanding of the full QlikView offering specifically in terms of ETL, are fundamental for a good QlikView implementation project.

BI implementation projects using QlikView are normally faster to execute and faster to get the customer to perceive its value. However, it makes sense to start with a smaller investment specifically on QlikView licensing, as modeling the data and implementing the ETL part is still the biggest bottleneck. It doesn’t make any sense doing a big investment in user licensing, when the real use of QlikView still depends on getting the data to make sense.

Make sure you have your data straight - think like Kimball, but act like Inmon - before moving to QlikView.

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.

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.

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.

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.

We use this solution for ETL, Analytics, Reporting, Automation, Integration between data sources (cloud, local, spreadsheets, etc), Data Scrub for Migration to new software, and automation of sending files to banks instead of using EDI, Positive Pay, etc.

This solution has simplified getting to and understanding our data, no matter where it is housed.

The most valuable features are the ETL, automation, and ease of use by the user population.

This solution would be improved with the inclusion of a feature that would allow us to add a common library of (our) commands used in load scripts and expressions, so with a keyword, we would get a drop down to select the command we are looking for, as opposed to the generic help. I keep them all in OneNote now and copy and paste them in, then change the field names. This addition would really save time.

examples:

Convert date-time stamp to just a normal date in the Load script - so we can match to the company calendar for Model Year / month etc , Fiscal Year /month / week of year/ week in year

date(floor(DTTMSTAMP),'MM/DD/YYYY') as TransactionDate,

Storing QVD's: (this is the path needed from a Data Loader)

STORE SummarySalesAggregate INTO [..\QVDData\SummarySalesUnitsAndDollars.qvd];

Sorted and Count for creating Arrays:

SortedAndCounted:

Left join (SummarizeSales2)

LOAD

Option_Inv,

Line_No,

if(peek('Option_Inv',-1)<> Option_Inv,1, Peek('counter',-1)+1) as counter

Resident SummarizeSales2

Order by Option_Inv asc, Line_No asc;

excellent

excellent

I have never worked with Qlik Customer Service directly.

no

it wasn't bad. We did need some consulting advise on the set up in the server...but designing the organization and naming conventions should be up to you.  We took the consultants advise and ended up renaming, changing almost everything as far as naming conventions

started with a consultant, didn't use them long.

keep working with the Company to get the pricing you need.  

yes - many

I have used QlikView to create powerful and compelling data visualisations. QlikView is a well-rounded tool with good visualisation component and data preparation features.

Using QlikView, we have been able to derive the value out of our data much faster than with other tools because of its easy to understand/use components and features.

As a developer, I liked that using QlikView, I had the option to prepare data myself instead of always depending on the data team.

More/newer visualisation components need to be added. QlikView's ability to embed custom visualisation is not a great experience.

• In-memory analysis
• Associative database query
• Easy to use
• Easy to install
• Easy to maintain

Amazing fast response to complex business questions due to flexibility and easy to use.

We have increased our revenues by 30% because the rapid and effective insights provided with the analytics we built with Qlik.

I would like to see embedded predictive analytics models or more integration, connectors with advanced analytics platforms.
Qlikview is extremely good with descriptive analitycs. But when you need to predict using advanced predictive models like Logistic Regression or CART or decision trees, R and SAS institute for example are good at it, so if Qlikview would have this capabilities embedded or connectors to integrate with them will be a killer product.

I have used it for nine years.

I have not encountered any stability issues.

I have not encountered any scalability issues.

Technical support is outstanding.

I did not previously use a different solution.

For the value you can add to your business, the TCO is low. There is a high price perception in the market, but this is relative.

If you do not take advantage of the solution, it definitely will look expensive but if you do, you will be happy.

For three months, we evaluated several solutions with installations provided by vendors such as Oracle BI, IBM Cognos, and SAP BusinessObjects.

The main challenge to prove during that phase was the ease of use without professional services support at that stage!!!

I highly recommend this solution.