QlikView Reviews

We primarily use the solution as a BI tool. We use it for data visualization.

Technical support is good.

The user interface and dashboards are very good. 

There are no issues with management monitoring. 

The solution offers good documentation.

We find Tableau to be a bit of a better solution. QlikView should try to be more like that.

The solution is quite costly.

I'm not sure how long I've been using the solution.

We have our own engineers and support from our tech department, so we've never had any issues dealing with the technical aspects of the solution. That said, they're okay. We're satisfied with their level of service.

We're also currently using Tableau. We find it to be better and easier. It's also less costly.

We want a few things that just aren't available on this solution, so we're moving more towards Tableau as our product of choice.

We have exceptional staff on hand that handled the implementation and deployment. They didn't have any issues with it. For them, it was straightforward. It wasn't complex for their level of expertise.

We handled the initial setup ourselves. Our internal team is very knowledgeable and can handle the implementation of new technology. Adaptability to new solutions is very easy for us.

The solution is expensive to use.

We're just customers. We don't have a business relationship with the solution.

We're actually thinking of moving off it and onto Tableau.

I'd rate the solution six out of ten. It just doesn't offer us what we need right now in terms of functionality. Tableau is a better fit for us.

We are active in the Hospitality Industry in Africa and we use QlikView primarily, for the time being, in our sales and marketing environment. We are situated in multiple countries and in multiple locations within those countries running on multiple sales systems. Each sales system has got its own features and capabilities. 

QlikView permits us to consolidate all the sales systems together onto one platform and enables ease of access throughout the whole company anywhere in the world. Moreover, QlikView makes our complex data infrastructure understandable for everyone.

QlikView allowed us to determine the sales date which was missing in the biggest sales system. QlikView helps us with detecting shortcomings in data capturing and safeguard our margin. It also enables us to forecast our sales, our revenue, and our cash-flow. 

Our Qlikview applications help us to get a good idea of our Client Base Performance and assist us in the decision making for Seasonal Specials. On the other hand, QlikView helps us to get a grasp on our Suppliers and helps us to negotiate pricing with them.

It enables quick and easy access anywhere in the world in real-time. We have satellite offices on different continents with a different time zone which makes it quite a challenge to show real-time values.

QlikView is for the end-user easy to use; a few clicks suffice to answer the question at hand. 

QlikView has got a very intuitive approach of visualizations, both from a developer's point of view as well as the end-users. It makes complex data easy to understand with little prior knowledge of how reading graphs is required. 

QlikView lacks the development aspects that its sister product QlikSense has got. It would be nice to also get the new graphs that are available in QlikSense in QlikView. 

It would be nice if QlikView could be plugged in into the company's website or an online portal such as QlikSense is capable of. There are ways around but it takes enormous time to develop.

Certain features such as a cumulative result, as is possible in QlikSense, would be nice to have since it takes quite some time to get this right from a developer's point of view.

I have been using QlikView for five years.

It is very robust.

The scalability is quite good, QlikView is fairly versatile yet robust at the same time and can be applied on multiple levels

Did not need any of this yet.

Setup itself was fairly complex since our company battled with a legacy of dirty data and a lack of data literacy.

Implementation happened through a vendor, and their expertise was/is top-notch.

No idea, I haven't made the calculations yet since there have been multiple system changes simultaneously and therefore difficult to determine what is the result of which improvement.

The setup costs for QlikView are fair as are the yearly maintenance fees. The licensing becomes a bit more expensive and requires some planning for onboarding.

I don't know, I was not part of that process and not active within the company.

Since Qlik is focussing more on QlikSense, it is recommendable to look into that direction than into QlikView.

We were using QlikView for reporting purposes.

The language support is very good. It understands more languages than other products.

The customization features are good.

The performance can be improved.

There is no automation or drag and drop functionality. 

I have not been in contact with technical support.

I have heard of other reporting tools like Tableau but I do not have experience with them.

When you are setting up QlikView, the first thing that you need to do is connect to the database. The length of time it takes depends on the size of the data. We found that for a million records, it will take between two and three minutes.

This is a product that I definitely recommend.

I would rate this solution an eight out of ten.

My company uses this application mainly for reporting and analytics through customized dashboards that meet corporate identity needs. The reports were created using existing SQL scripts that powered legacy dashboard and reports (i.e. SAP Crystal Reports).

This is a very cool application with endless options for creativity and visuals. 

While this application was loved by the end-users, the development required to build these dashboards proved to be more difficult vs. other solutions such as Tableau. 

My company is big on dashboards and this application excels in this space. Endless customization is key to meet everyone's needs. I also like how the application can use existing SQL statements to use as your root data/tables/information. Compared to other competitors, this solution can do more.

I really wish the application was easier to use in the development phase.

Our business model relies on the business to build their own reports and many departments did not have the associates they need with this type of skill set (i.e. SQL experience). In a business model where a centralized department (i.e. IT) is in control of the reports for the entire company, this would not be a problem.

The development was the ultimate reason this application did not take off in my organization vs. a competitor's application (Tableau). This is a shame as the finished dashboard appeared to be more polished.

My experience is limited but from what I experienced, stability is very good.

The scalability of this solution is very good.

Very reactive, quick and supportive.

I have been 110% satisfied every time I have reached out with a question.

We started form SAP Crystal Reports and originally moved to Qlik as a replacement, but this application proved to be more difficult for development as the business owns their own report vs. IT.

Application install was simple and straightforward.

We implemented this solution with our in-house IT staff.

No ROI as we have moved on.

The biggest comparison was made with Tableau, which ultimately won.

Their training and services have been top-notch and very reactive.

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 developed an application for a hospital to improve the potential of analysis of that company. I used Windows Server 2008, 8Gb RAM, two processors.

The hospital improved the quality of the data analysis and increased its profits, because, for the first time, they were able to analyze consistent data.

• Speed of development
• Ease of learning
• Low ROI
• Fast deliveries
• Scalability
• Multiplatform, and speed in queries.

• Improvement in the graphical user interface
• Introducing HTML 5
• Context sensitive
• Drag and drop visualization
• Responsive design.

Our primary use case is an application that our users use to get the profitability on a monthly basis.

It's pretty easy to deploy.

I would want them to have more options as a user. It would be nice for them to create their own dashboards and add fields.

I did not encounter any issues with stability of the product. 

I did not encounter any issues with scalability of the product. 

We usually use a partner for technical support, so I cannot really rate the service. 

We had the partner help us set up the product for us. So, I do not remember any difficulty with the setup process. 

It is not very expensive. I think it it is on par with other similar products on the market.

So the primary use case of QlikView, I have worked with financial maintenence.

You can do a lot of things at the back end which are not possible in the other solutions in the market.

Tools that can be improved are:

• Visualization charts
• Pricing
• UI transparency

The Qlikview is quite stable in comparison to other solutions.

It is a very good scalable solution. 

The tech support is strong. The logs of the documents are helpful. 

I have some prior experience with Power BI and Qlik Sense.

The initial setup is not very complex, it is on a moderate level. If others compare it to other BI tools, they may find it complex. But it was not a problem for us.

The pricing is too high compared to the other solutions on the market.

There are features of QlikView that are not available with Power BI or Tableau. There are activities on the back end that work better in QlikView.

You can do a lot of things at the back end that you cannot do with other competitive solutions.

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.

Our sales reps use dashboards for reporting latest inventory quantities on a real-time basis, which is critical for the business.

Time and effort are reduced using QlikView by saving a lot of money providing the same information before an implementation.

• Datamining
• Fast data loading of million of rows
• Incremental load
• Scripting as per a customer's need, which is a pretty cool feature and not available in other tools.

• Bookmarking
• Data load window and more information to be used while loading huge data.
• Installation and deployment could be made easier and quicker.

No issues.

No issues.

Support is very good.

It is better in all aspects than our previous solution.

Not sure.

Qlik is fairly high in terms of pricing.

We evaluated MS Excel.

Overall, it is an excellent product.

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.

Speed of in-memory processing
Associative model - no more cubes
Speed of development

We create BI solutions so our customers benefit from solutions that are delivered in weeks rather than months and we look good by providing timely value-for-money solutions

Although Qliktech's road map clearly states that QlikView has a long way to go, most of the R&D effort seems to be benefiting Qlik Sense which is getting stronger and sexier with every release 5 a year from now - June 2017).
Qlik Sense makes selling "Qlik" easier - the only "negative" aspect is that the "self-service" capability of Qlik Sense means less consultancy for our company but more customers!

8 years

Rarely

Almost never

No

Customer Service:

Excellent

Technical Support:

Excellent

Microsoft BI stack (SSIS, SSAS, SSRS)

Setup is straightforward especially with later editions of QlikView

In-house

N/A - we are resellers

Tableau

Gartner and others have a good reason to rate it so high. Amazing product.

Its ability to build, very quickly, very complicated models. In our case, we use for this modeling for the calculation of cost allocation and transfer price and the like. It is very helpful. It's a really powerful tool in modeling creation.

It has helped us to implement the accounting management system and provide a very comprehensive solution for this. Also, I already mentioned cost allocation system, transfer pricing.

It's also very helpful in visualization of the data from our operation systems. Because we are a bank, data creation is very important for us, so it's another model.

It covers many things, including current exposure, the coverage of loans, etc. In these areas, it's the most comprehensive and most helpful of the tools we're using, based on this platform.

I would say it's not negative, but it's an issue because we also use other tools, like SAP BusinessObjects, for a long period of time, which is another product in the business intelligence area.

Improvement in collaboration, between that and publishing of reports and publishing of models. Probably that could be more comprehensive, from my point of view.

Four or five years, already.

Yes it's stable. Not 100% but, really, compared to other products, it's a stable product. It's controllable. And the maintenance received from local partners is very good, at a very high level.

No problems.

We have both technical support and support in the development model from the local partner of QlikView. I would rate it at a very high level.

Because the majority of BI tools are focusing on processing a significant mass of data, we were looking for a more analytical tool with the possibility to quickly build models, and we found it. On the other hand, QlikView has some constraints due to the architecture, so it may not be applicable for millions and millions and millions of data records because it requires significant expenses for the hardware. But, as an analytical tool, it's very interesting.

It was very easy because we started by using the free version of QlikView. After that, we bought everything, including a server license. So, we had no problems with this.

At that time, we already had BusinessObjects as a BI tool in our bank, with SAP Crystal Reports, for example, as a part of BusinessObjects. At that time, in the market, there were no alternatives in this respect, so our choice was very precise because already we used this tool and we decided to buy it.

I would recommend this product. We have a lot of reference meetings because we were the first bank in the country to implement it, this platform. So we're meeting our colleagues who are working not only in the banking industry but from telecom, from the pharmaceutical industry, etc. We recommend it.

It's one of the best products in this segment, for BI, for the automation of analytical activity within the bank or within the company. It doesn't 100% cover everything, but in the area, it works very well.

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.

The dynamic way in which you can analyse data.

We are now able to get information when we need it without running reports or it taking a huge amount of time.

Cost: The licenses are expensive.

Eight years.

No.

Only due to the costs.

An eight out of 10.

Straightforward.

The system needs some technical expertise to set up and can be expensive, but once set up, it works well.

Ability to connect and transform data from a variety of sources into the same application. From an analytical development perspective, there is a wide scope to create complex calculations within chart expressions, (including recursive expressions), which, combined with the trellis functionality, means more output with less setup effort.

A well designed app brings freedom of inquiry to meetings, allowing me to answer questions in real time and this has transformed progress and outputs of our monthly group meeting.

Finally, it really is a case of data instantly updating upon selection. No more watching an egg timer as a server churns away.

Meetings are now proactive rather than reactive with analysis conducted straight away. We're making better informed decisions - and more of them!

I have automate a complex set of analysis within a matter of days (as a relatively novice user), that had taken weeks, with less useful outputs, in other software.

Syntax editor needs some work, it's frustrating to have valid syntax being flagged as incorrect. It would save time troubleshooting errors that don't exist when the script runs or charts render.

1 year, but not a heavy user - though this will change!

E-T-L, The Extract, Transform, and Loading capabilities of QlikView make it a highly sophisticated self-service business intelligence tool for developers and analysts who desire much more advanced handling of dirty or unconsolidated data. QlikView scripting language has numerous transformation functions.

As a consultant for my organization using Qlik to design management dashboards, analysis and ad-hoc reports, I have seen the way it has helped many of our clients get the desired reports and analysis for their stakeholders and top directors which would normally take time and more effort to get.

The user interface and ease of use takes a bit of a learning curve to pick up. There is no drag and drop functionality at the development stage unlike its competitors. Maybe QlikSense could handle that area.

We have been using the solution for five years.

We haven't yet encountered any issues with stability.

QlikView is a memory intensive application and does sometimes start to weigh on your PC resources. Also you would need to learn some development tricks to manage unnecessary time wasting when loading large database sources, like the use of QVD – QlikView proprietary data format - for faster and efficient loading times.

The Qlik community is very vibrant and you find or get answers to most issues started or any other areas.

We did not use a solution previously.

The initial setup is pretty straightforward for personal use, except when you are looking at deploying the QlikView server which will entail some configuration instructed during the installation process.

QlikView pricing and licensing is on the high side for a small sized company, but it's competitive among its peers.

As a consultant in the area of business intelligence and data analytics I have had to personally evaluate QlikView with other self-service BI tools such as Tableau, Power BI and MicroStrategy.

Invest in the memory and RAM of your PC or server you intend to use for QlikView. Ensure you have all the necessary resources and connectors installed for proprietary databases.

Data transforming with scripting, and the associative model that lets users browse data in an easy way, are the most valuable features.

Linking different sources of data in a way we could not do before has really helped decision-making regarding our production and focus.

• Error handling

I have been using it 10+ years.

We have not really encountered any deployment issues.

Sometimes when developing QV applications, I encounter almost unexplainable errors that causes QV to crash.

Customer service is very good.

Customer service is excellent.

An in-house team implemented it.

• Better business

To take a good look at needs and the alternatives.

• The search feature: ability to see the related data

We were able to see tremendous insight in our sales dashboard at deployment.

• Data cleansing
• Better source data connectors

I have used it for 2 1/2 years.

We have not encountered any deployment issues; we had an experienced deployment partner.

We encountered a memory issue.

We have not encountered any scalability issues.

Customer service is outstanding.

Technical support is great.

We previously used Tableau. We switched because the business requested Qlik.

Initial setup was pretty easy because our implementation partner understood our current data source (SAP).

A vendor team implemented it.

The time gained from reviewing massive data can be used elsewhere.

Pricing is a bit too high and I think licenses should be unlimited.

Some of our users were on Tableau.

The most valuable features of this product are: its data modeling capabilities, the associated search function, various charting, the flexibility of doing sales in object, section access, and drag & drop storytelling.

We have been using Qlik for most of our front-end solution since adoption; people like it a lot.

I would like to see:

• Mobile and smart device delivery
• Set analysis simplification

I have used it for 3-5 years.

Performance sometimes is a concern.

Occasionally, it hangs while running a script and it bounces out.

Technical support is OK. We work with a vendor partner. We have no direct interaction with Qlik.

We used IBM Cognos BI, in which charting and dashboarding are painful.

Initial setup was very easy.

A vendor partner implemented it.

I advise your team to dive in and learn how to build the most-efficient data model, and learn how to design your web pages.

• Integration capabilities
• Speed
• Amount of data that can be accessed within in a few clicks

Working in the IT environment gets challenging especially when you have multiple sources of data that you need to combine. QlikView makes this really easy and simple to do, because QlikView has its own ETL modeler built into it. Having an all-in-one tool is quite an advantage.

QlikView has made it possible to look at large data volumes without having the drawback of strain on the database and waiting long periods for data discovery. QlikView has also helped people switch over from reporting to do more analysis and data discovery. QlikView has also helped serve as an alternative to Excel reports.

This is really an awesome product, but there is room for improvement regarding the visual aspect (this has been sorted out in their new product – Qlik Sense). Some features are a bit tedious to achieve results, especially for new users and people who have not had training or experience in using the product.

I have used it for four years.

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

I rate the level of customer service and technical support 9/10.

Initial setup was straightforward. I would recommend getting someone from Qlik to advise or do the initial setup to eliminate any issues.

Get Qlik to do the initial setup.

I also looked at Tableau, Sisense, and SAP BusinessObjects. Tableau is a good tool, but has a few drawbacks when your data source is not in the correct format. BusinessObjects is a bit old school (reporting) and SAP HANA is costly to implement. BusinessObjects is also costly and requires a lot of work in the data and business layer.

Determine what you require and get the tool that suits your need the best. Compare products and if you decide to go with Qlik, I personally prefer Qlik Sense. Again, this depends on your business need.

Data Discovery has allowed us to enrich the analysis of data and discover new ways to generate new KPIs. It has also helped us to discover some critical points in our processes.

Using QlikView models, we've improved after-sales service in several of the products we offer, and we have managed to measure the profitability of our customers.

There’s room for improvement with the licensing, as well as memory consumption for certain objects and technical support.

I have used this solution for three years.

I have encountered issues with scalability. We have generated models with large amounts of data and have found that the processor and memory of our server has been declining. We do not have something to help us to size the equipment requirements when a big data model is developed in QlikView.

Technical support is good, but needs to be better for our local service.

We are evaluating Power BI suite and Datazen. We found that these products offer a good level of analysis, but the licensing offer was the deciding factor.

A vendor team did the implementation.

We still do not see a significant ROI.

Make an accurate sizing analysis of information, with a view to growth.

The most valuable feature is its flexibility to develop dynamic analysis, gathering information from different sources, such as spreadsheet, database and internet.

With QlikView, my organization is able to track information related to service desk tickets and SLAs. This information helps us find the bottlenecks and fix them.

Reports module should be improved to make it user-friendly and easy to develop reports.

I have used it for eight years.

I did not encounter any issues with deployment, stability or scalability.

I rate technical support 8/10.

We used to have IBM Cognos, but we decided to go for QlikView because of the flexibility and the short time to develop and delivery analysis.

Initial setup had medium complexity due to different data sources and integrations.

We developed it in-house. The advice I would give is to get the business user (internal client) as close as possible and in parallel for any doubts and questions about the tool. Visit QlikView forums We have a lot of useful information on it.

Proper planning is the key for choosing the right license for the right user. Know your internal clients and their ability to do/create analysis.

It's s one of the best solutions for short-time deliveries.

Real-time reporting is this product’s most valuable feature to me.

The decision-making process has been streamlined.

The forecasting accuracy should be improved.

I have used QlikView for one year.

I did not encounter any issues with deployment, stability or scalability.

I rate Qlik’s technical support on the high side.

Initial setup was straightforward.

We did it in-house, which I prefer.

It’s about each and every individual and organization.

Extraction from almost all data sources provides a lot of value to me. Ease of operation, data modelling and creating dashboards with simple objects and the abundance of visualizations are also valuable.

We extract our data from SAP BW as well as Update 7 data source. Extracting and associating these data to form Main Data Model is quite simple. The objects that QlikView provides can be used to make complex KPIs for visualization. Apart from these for visualization, we also implemented many extension objects of Maps with our QlikView applications.

We managed to implement applications combining CRM (Customer Relationship Management) data and sales data from two completely different data sources. It's the first (small) step towards big data. CRM data comes from Update 7 and sales data comes from SAP BW, which made it tricky to combine them and make common navigation possible.

I would like to see JavaScript or jQuery features added to it.

Dynamic changes with respect to page scrolling, responsiveness and actions related to it are what I am expecting in the next version.

Other than these, while adding named CALs in QMC, it would be really great if we could load all of the names from a single file (for example, an Excel sheet) together all at once.

The iPad application lacks some features. For example, container box object functionality does not work properly in iPads.

I have been using this solution for more than 13 onths.

We had issues. After deployment, while extracting data from SAP BW, a timeout error occurred many times. We haven’t found any solution for it. So, we have to keep reloading the job on QMC until it gets successfully reloaded for the day.

Franky speaking, I have never contacted technical support.

I did not use a different solution before Tableau. This is the first tool I have used for BI.

I was not involved in the complete setup. However, its installation using multiple transports and connectors is quite straightforward.

We implemented it with the help of a vendor team. (QlikTech)

Deployment and configuration of this tool is very simple. The tutorials that come with the installation of the product are very helpful with creating dashboards and learning about the product in short time.

QlikView’s associative model is a fantastic design that enabled the Green/White/Grey feature. This feature greatly helped us highlight the relationship between different kinds of data.

To further explain the Green/White/Grey feature, let’s take a sales report of an electronics shop as an example. In this report, it may have dimensions (Product Category, Salesman) and expressions (Sales Qty, Sales Amount).

Green means the values of dimension that you have selected. Under the Product Category dimension, it will have different values e.g. Smartphone, Laptop, Desktop. If we want to see the sales performance of Smartphone, we can click on Smartphone, then it will become green. We can also select multiple values e.g. Smartphone and Laptop in the dimension.

White – shows the values of dimension which are related to the another dimension values that you have selected.

Grey - shows the values of dimension which are NOT related to the another dimension values that you have selected. By following the previous example, we have selected Smartphone in Product Category dimension. In the Salesman dimension, Salesman e.g. Jeremy or Janice who have have sold Smartphone will be shown in white color. Another Salesman, e.g. Roy, who didn’t sell Smartphone will be shown as Grey. This is very useful for us to identify relationship between dimensions

Its “Search Object” function is also very useful for us to search for the information we needed.

“Section Access” is another great feature as we can identify user authority on accessing data in an easy way.

Another feature "Set Analysis" which enabled us to configure different behavior for each dashboard. So that some dashboards (e.g. YTD) can be freezed and not affected by some of the filter selections.

My experience using QlikView was in a F&B chain store with outlets around the world. In such a F&B chain store, there are a lot of dishes and they are changing frequently with a high transaction volume.

In such an environment, a search function is very helpful for us when we want to find out the sales performance and trend of a specific dish.

Qlik’s associative model greatly helped us identify customer purchase behavior and we can define combos according to this information.

By comparing with the latest data discovery tools like Tableau, Qlik Sense and Sisense, the layout and colors are not eye catching enough. It looks like a very powerful excel with a lot of powerful features for analysis. But it may not be good for presentation.

I used it for two years.

Qlik is able to import data directly from a transactional database and create joins between the tables in there. However, I encountered a performance issue with high volumes of data.

Therefore, I suggest designing a data warehouse and use it instead as Qlik’s data source. The performance will be much better.

Actually, I can’t remember any issue that I was required to check with customer service or technical support. For nearly all of my questions, I can get answers in the Qlik community.

I have previous experience with IBM Cognos. It was a very comprehensive solution that can be used for pixel-perfect reports, email schedules and also data analysis. However, there are many more development and implementation steps than with Qlik.

Also, Cognos requires a steep learning curve even for a user with a technical background.

As we wanted an easy and user-friendly self-service BI solution, QlikView is more suitable from this perspective.

On the server side, it is quite straightforward and we didn’t encounter any problem.

On the client side, the user can access it by browser or a desktop application. For the desktop installation, it can be downloaded from internet. And the configuration to connect the server is very easy; even end-users are able to do it. We prepared just one slide and end-users are able to follow it.

We implement it through a collaboration with the vendor. The vendor team is responsible for installation and configuration. And the in-house team is responsible for development.

My advice is to use a data warehouse as the data source, which can greatly reduce Qlik implementation time, as creating too many joins in Qlik is not a best practice.

My advice is to start small with the named license scheme as the price is much cheaper and it will be much easier to gain management approval.

People who have interest on QlikView should also take a look on Qlik’s another product Qlik Sense. They have similar features (e.g. Section Access, Search function, Associative model).

QlikView relies more on the IT side. IT builds the base and a majority of end-users make use of it. Some power users can build dashboards, share with others and create formulas in there.

Qlik Sense is a self-service BI tool. It is easier to use and stronger in visualization. But some advance formulas might not be available.

The ability to provide drill down functionality quickly and easily into large data sets. Anyone working with a large amount of data in Microsoft Excel and then waiting ages for it to subtotal all that information, will certainly appreciate the speed and efficiency with which QlikView handles data. Users can get a lot more done, and a lot more data can be analysed in a shorter period of time.

The fact that QlikView provides its own QVD structure, as well, removes all dependency on having a DBMS in place before implementing QlikView – so it is cost effective.

The fact that QlikView can literally plug in to so many different types of data sources, as well, is a definite benefit.

The facility to auto-reload at scheduled times is great too!

My company was recently bought out by a competitor, now forming one group. The organisations are on different versions of a particular ERP solution, and the need immediately arose, from a regional and management executive level, for a dashboard to measure the sales performance of the group as a whole. Using QlikView, we managed to pull information from two different servers - one running off a QVD file structure, the other using a Microsoft SQL Server - and provide a consolidated sales performance model. This allows our executives to be able to examine the performance of their companies from a central point.

Some improvement to the user interface (for the developers). It could certainly use a re-vamp. The existing tab structure can be confusing sometimes and the controls that you would expect to find on one particular tab are actually on another.

I'm referring to the properties of the various charts that you can create within Qlikview – this brings up a dialogue box with a number of different tabs along the top;

In my opinion, for example, the tabs “Visual Cues” and “Style” could be combined into one. “Caption” for another example could be renamed to “Title Bar config” or “Chart Config” or something like that. Some aspects of the “Layout” tab could be added to “Presentation”.

The dialogue box itself isn’t quite wide enough, so if you end up going all the way to the right you have to click on an arrow a couple of times to see the tabs all the way to the left again, and you can’t resize it either – Why???. The box itself should be wide enough to encompass the number of tabs in a single view. Either that, or have a maximise / minimise buttons on it to give the users the choice.

There are no doubt a few others I can point out if I give more though to it, just my feeling of the product is that it can be a little unwieldy, especially to people initially learning the program.

The company has had the solution for the last five years, I have been involved for the last two.

No issues encountered, the solution is stable, and the users are happy with the solutions provided.

Customer service and support from QlikView South Africa is first rate. They respond quickly, and are always friendly, professional and very efficient.

QlikView was this company’s first foray into making use of an external business intelligence tool.

The setup is fairly simple, but you do have to have a decent level of technical knowledge if you are going to set up a Qlikview Server yourself. Otherwise, I’d suggest the use of a consultant. The client software is very simple to set up.

We implemented through a vendor. The advice I would have is to ensure that you attend all necessary QlikView courses (i.e. designer / developer), to get a very clear idea for yourself exactly how QlikView works. Sometimes sales consultants will over-sell you on the bells and whistles of a product, and when you actually want to make use of it in a particular way, you might not be able to. This has not been the case during our QlikView implementation, but I have experienced other implementations that have been like this.

So you do need to be very clear on:

• What exactly do you want to get out of a business intelligence solution, what data do you want to manipulate and analyse, etc.
• For your own sanity, be very clear on how QlikView works and that you will get the solutions out of it that you want.

One cannot really place a monetary value on the depth of very valuable information that QlikView can help you extract. My advice also would be to be very clear on the licensing model you want to go for. The QlikView licensing model is complicated, so be sure that whoever is selling QlikView to you explains it thoroughly.

I would suggest having someone in-house doing the development of your models for you, be it dedicated to that role or in addition to another duty. Nobody understands your business quite like you or the people working for you, and that is always advantageous when building solutions for the business. Not to put down external consultants, but doing it this way can save you a bundle into the bargain.

Strong visual capabilities, drill down function and data browsing. No need for any other tools, ETL/ scripting and visualisation built right into one tool.

• Ability to monitor progression towards certain deadlines and preset thresholds.
• Ability to browse through the data by selections to quickly answer questions.
• Easily export to excel or print for external use.

While Qlik and their products are very intuitive and a pleasure to use as a developer of the dashboards and poweruser, many of my colleagues and stakeholders of information are used to static (paper) reports. This often leads to producing tables and graphs that are 'pinned down' (set analysis) to reduce the flexibility of the representations and the dashboards as a whole. (Qlik presents this as a core strength of their products.) 

Often this makes the formulas for these expressions and dimensions very complex. Of course you could argue that the users would have to 'mature' to use this new, more flexible, way of information. But it would be a great improvement for the Qlik products if it were able to easily 'lock' graphs without extensive coding.

Over 5 years

Due to in memory technology, when datasets get really huge, rendering of graphs can take some time or even return out of memory.

• 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.

• Ease of use for end user
• Analytical reporting
• Easy-to-build dashboards
• Self-service reporting
• Speedy deployment

The PoC for a new business area was not covered by the management reporting platform (controlling of IT processes).

• Built-in monitoring of ETLs (there was no advanced tool for monitoring, planning and evaluation ETLs), I work with SAP BW (i.e. RSMO, RSPCM, ST13 transactions), of course there was an option to have additional expert tool but for a lot of additional money
• Formatted reporting (PDF and export to Excel) - if necessary compile aggregate export to PDF document was not allowed to draw and do parameterized output compile or schedule it as a job with an appropriate distribution to the responsible user group, custom printing to PDF or Excel did not correspond to reality/original

• Built-in monitoring of ETLs
• Formatted reporting
• Print to PDF
• Export to Excel

I have used it for half a year.

I had integration issues with SAP BW.

Technical support is very good.

IBM Cognos was the original MIS platform. Within QV, there are better analytical reporting features.

We implemented it in-house with some external support.

ROI is very long, > 5 year estimation.

Assess the possibilities, advantages and disadvantages of the product as a whole with regard to the general characteristics of MIS systems and considering plans to use a management reporting platform across the enterprise.

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.

The server load, the QVD load, ease of variable declaration, and the different dynamic charts are very valuable to me.

Our complete BI transformation and production was done through QlikView instead of basic Excel reporting and analysis, reducing manual input, ease of automation and more reliability in numbers, thanks to fewer human input errors.

Currently we are building a pane to use filters and select options. For a dashboard, if they would add a "Column value" filter option like what you see in Amazon on the left hand side, that would be useful.

It could also have an autosave feature, which it direly lacks.

A direct feature to export views to PowerPoint, instead of external plugins, could be useful.

Sometimes large files are difficult to read and QlikView crashes midway. So you need to start from scratch. Instead, if it could support reading and processing large files with a lot of records (4 million +), that would be useful. This was one such issue we faced while doing a BI transformation as the data generated was huge.

I have used QlikView for 3-4 years now.

We did not seek technical support. I simply researched answers in forums and through Google searches, blogs etc.

With the help of IT teams, the QlikView online servers were set up (one for production, one for testing). So, implementation was done completely in-house.

ROI can't be measured directly, but the power of BI can be visualized through QlikView.

I personally feel the QlikView server license is extremely expensive and might not be affordable for most organizations. However, all clients felt QlikView was so easy to operate, see results live and visualize in great charts, easily copied to PowerPoint. They were able to easily log in, select their regions, time period and view the results in a single shot instead of viewing multiple Excel reports and looking up, etc.
They used bookmarks for their filters and that made it even easier, rather than entering the inputs every single time.

We evaluated Spotfire, Tableau and finally chose QlikView to be deployed for all dashboards in the organizations.

QlikView can be a powerful tool in your organization if you are serious about a complete BI transformation and moving away from standard Excel reporting.

Given standard training and experience, migrating to QlikView is a very good choice.

The ability to capture data from multiple sources, quickly link by key fields and quickly analyse in a dashboard proved to be such powerful features that we reduced the use of Microsoft Excel and Microsoft Access almost entirely for any kind of reconciliations.

I worked in a financial institution having most data in mainframes but also having extracts and datasets put into various places from highest quality Oracle and MS SQL server objects right down to MS Access/Excel and continuing to Text File output.

Sometimes for either quality control purposes daily or some other kind of reconciliation or verification, QlikView was great for a basic end user with minimal skill to bring that data in and map it as necessary to achieve the desired result. (Often the datasets easily map via a couple of primary fields that the business users understand and outside developers may not understand without a business analyst specification)

Most times making that ad hoc effort a template of some sort and making mundane roles like daily recons be easily achievable.

Doing this same work in MS Excel or MS Access can be tricky and dangerous and not be as intuitive for non-technical people. Doing it other ways can end up being too much effort with hiring developers and building systems and paying for a lot of developer man-hours when a quick QV dashboard does the trick by the business end user.

This product improved how my organization conducted repeatable analyses, such as a user access internal audit review for 500 users over 100,000 user ID and system access across 50-100 systems. My first project before we had QlikView took about a month, but after we rewrote the procedure using QlikView, it was much better and took about a week. We pretty much used the same raw data, but the report and analysis was so much quicker.

The process of gathering the data and using Microsoft Access used to take a month or so. Certainly, using QlikView as an ad-hoc tool is very powerful, yet easy. Comparing it to development on Microsoft Access, it feels about 10 times quicker. You go from raw data almost directly to reporting. (Skipping the hassle of lots of queries, forms, and slow report creation.)

As they say, "Seeing is Believing”.

While it used to be extremely easy to work with for me, at least the basics, some other folks used to have a bit more trouble using it. I think that it might be useful if the first-time user wizard was a bit better. It might help people get the “Eureka “ moment on their own. I always felt that the wizard was not really worth using, and I started people off with making their own import scripts with my help. Others also seemed to believe that as well.

I think the wizard could take a bit more time and provide training along the way. For example, show the data to be imported, and go over some of the best practices. And maybe continue on with going over the Edit Script and hit some of the basics there as well and so on.

I think all things are covered in the tutorial, but I had very little success having people use the tutorials.

Some aspects are so common, and used so much:

1. Basic import of data, load, review the field names that come in, set your fields as “what you want”
2. Import a different table, review as in step 1, but check for synthetic links, do your “AS” statements to clean up, and get the linkages you want, etc.
3. Then have some wizard to make tables and charts in the same way, etc.

I do these things with new users inside of a couple of hours, including usually helping tham make their first solution.

I used QlikView for five years.

Never has this been a problem, but mostly in our company, we focused on using QlikView standalone.

We had tons of core and server architectures, and QlikView was used to improve reconciliation and quality control.

Ultimately, there is great power in using QlikView to be an enterprise solution (in the right context). But the user base was able to get so much productivity out of our approach.

And to get an enterprise solution in place required a budget and resources, which we did not have.

Technical support is excellent, the user groups are really good, and outside of that, there are excellent web resources via YouTube (e.g. AnswerSharks) that have evolved.

In reference to user training, I sent people to these sources even more than to QlikTech themselves.

I left my firm just before QlikTech was finally given the go-ahead to design some product solutions for us. (Having ad-hoc users design things worked, but it was time to get more polished internal- and customer-facing solutions to take us to the next level.)

As a global firm, we actually looked at many products, even signing a multi-year contract with a QV competitor (Tibco Spotfire, but the enemy of efficiency for analysis is MS Excel).

For SpotFire, it was always my opinion that that deal was done on a golf course, because QlikView over the years was the better product by far (certainly, all users loved it) versus the other product, which very few users understood, and certainly users did not show anywhere near as much affection for it.

We went for standalone licenses in the beginning of about six, and over several years the license count grew to 60. When I left the company in late 2015, we were looking finally getting a server.

I do not know the status now, but the company should have been given serious thought to getting a server, and perhaps converting some of the licenses to QlikSense.

A vendor team implemented it, but it was more like a sales team. We just asked for more licenses and put the server deployment on hold for way too long.

Although users were very happy, the cross-division expansion that I felt was possible never happened.

The biggest problem out there is that most people keep thinking, If it ain’t broke, don’t fix it. I believe that people use MS Excel way too much, and that is a symptom that something is broken.

Also, I used QV to pull data out of core systems often whenever reconciliations were questioned. (Analyzing the source directly is better than another Excel spreadsheet.)

We pretty much measured our success in man-hours saved or efficiency gains:

• We did not aim high, but certainly, I put together a number of solutions that worked flawlessly, and could save between 1-3 hours every day.
• More importantly, we applied this analysis tool, were able to benefit from very high quality analysis and recon, improving employer quality of life.

QlikView requires a little bit of “handholding”, which was provided via a small expert group at my last employer. (Originally, we got to a “Yeah, I get it”, Eureka moment after one or two two-hour, on-site visits from the sales support team. Add a phone call or two.)

I would suggest that while returns on efficiency would be quick, it is worth it to consider expanding the user group sooner, and having a strategy to grow the user bases very early on. I compared this tool to the over-use of MS Excel and MS Access to attempt to do similar things in my organization.

And while we saved lots of time and effort in the areas that QlikView was used, the real target I had was to take PowerPoint off its pedestal for management reporting.

We never quite got there, but I envisioned that dynamic usable reports was a much loftier goal than death by PowerPoint. (But it must be said that lots of executives love their PowerPoint, which has continued to mystify me.)

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.

The associative/relationship engine and fast performance are the most valuable features of the product for me. It is excellent for number crunching with basic visualizations and known questions.

QlikView is used internally for financially-focused groups. It has moved folks out of Excel land into interactive/shared analytics.

I would like to see improved performance/scalability at high data volumes + high user concurrency. Having only in-memory capability for hosting source data is a constraint.

I have been using QlikView for 2.5 years.

No issues with deployments/stability. Departmental-scope in use has it well-positioned here.

Technical support is very good.

Nothing else was reviewed, given the business area lead had previous experience with QlikView and wanted that for his department.

Initial setup is straightforward. It is not a complex system to install.

We used a regional vendor that had experts in the platform to help us install/configure/jumpstart our use, working directly with the business department in need.

ROI is unknown. However, licensing costs continue to increase in QlikView and in Tableau, which we also use, forcing us at some point to consider consolidating to one and/or turning some existing/owned MicroStrategy licensing inward to replace if the the upward pricing trend continues.

Pick the right tool for the job/consumers of the products. There is not a single product that can cover all personas/use cases well or there would be only one product out there commanding the world – and there’s simply not just one. QlikView is great for numbers-focused users who live in Excel today and want a better way to create common metadata and analytics that can be easily distributed/consumed by target users.

• Combination of ETL with powerful scripting options and a fast, flexible front end makes it like a Swiss army knife
• Powerful front end, which allows us to make very user-friendly interfaces
• The associative model, which allows for truly integral reporting

The combination of quick, agile delivery combined with a front end that allows you to easily drill through from high-level dashboards to low level details means that we can deliver according to the business case. Compared to our other tools (e.g. SAP BO), business users are using this tool a lot more.

• Chart types; some look a bit outdated, would love to see Qlik Sense- or Tableau-like visuals
• Central formula/measure repository, can now only be done with variables

I have used this solution for eight years.

Deployment is very easy and quite stable. Only drawback is that the server can stop functioning if not enough memory is available, so that needs active monitoring once you are close to the limit.

Good, quick responses and mostly the support team is very knowledgeable. You don't have to go through multiple layers that delay the resolution, like with some other products we have experience with.

We have everything, but the combination of functions in one tool as well as the good support and quick implementation times make QuickView our preferred tool for most use cases.

Straightforward, easy installation (next-->next-->next). Single sign on was a bit more complex, but way easier than with SAP BO, for example.

We have implemented it with vendor teams and in-house ones (multiple installations). For a simple scenario with one server, just do the training and you can do it yourself. For a more complex scenario (we have a cluster of six servers in the cloud), it is better to let the vendor do it; they have the best connections for the complexities of clustering.

License prices are quite high; it makes the roll-out slow as you first have to convince people of the benefits. When growing, session licenses are the best; we achieve a ratio of 1:30 for the average user.

Perhaps if you start from scratch, it is better to start with Qlik Sense, as it seems that most development effort goes into that product.

QlikView enables fast visualisation, analysis and navigation through data. It is very flexible, and offers easy-to-develop, quick-value tools for navigating and understanding data.

QlikView allows non-technical stakeholders to quickly engage with and navigate through their data as business information.

Data modelling is often a protracted process, with no toolset available apart from scripting. The consequent data models are not very portable at all.

I have used this solution for five years, sometimes more intensively than others.

One of QlikView's greatest strengths is its in-memory handling of large amounts of data. The flipside to this is some ongoing leakage, which makes it sensible to reboot once a week.

Qlik's support model for everyone except large enterprises is through consultant partners, so it depends on the quality of the partner. On the whole, they seem to be good.

It was implemented via a consultant partner. They were technically very good, but one should ensure the consultant delivers comprehensive documentation. A solution is only as good as the ability to navigate through it and enhance it as the business changes.

Although normal advice would be to mandate that the implementation deliver to business-specific requirements, it is strongly recommended to understand the product's great capabilities, and to exploit the competitive advantages of the product. Otherwise, it becomes just another business intelligence tool blindly shoehorned into a business that doesn't gain the best value and ROI from it.

QlikView’s associative ability. The AQL that QlikView uses to associate and ‘bring together’ similar data types (based on name) is extremely powerful and useful. One click causes a whole ripple effect though the whole dashboard, because everything is associated to one another.

We have used code to create a calendar effect. We then loop through that calendar, executing SQL at the end of each month. This is not easy to mimic in normal SQL, and would require an SQL package to perform such a thing.

QlikView allows us to perform these feats with ease.

QlikView does not work very well with very large data sets. I would like to see that improved.

I have used this product since Jan 2013.

Besides the stability issue with large data sets, I have not encountered any other deployment, stability or scalability issues.

Technical support is 3/10.

I have not evaluated any solution similar to QlikView (e.g. Tableau).

We did not previously use a similar solution.

Initial setup was straightforward.

A vendor team implemented it. They knew the tool best and we could get it up & running a lot quicker. Part of the implementation included training.

Not easy to answer. What we use it for, internal to the company, is to track internal costs as we manage quite a number of cost centers. We've successfully managed our budgets and have recovered quite a substantial amount of money for our CC as QV has allowed us to track incorrect CC billing.

QlikView really works well. We have had no complaints from users about its functionality. There has never (or hardly) been a time where a user makes a comment like “Oh, pity that QlikView can't do this…”

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.

It allows you to establish business data models on an associative basis, and to do on-the-fly analysis on associated data for deep understanding / insight.

For complex analysis, its scripting capabilities enable one to do complex calculation to present required information much easier than traditional / other BI software.

I have implemented both QlikView and Qlik Sense solutions for our customers/organizations in multiple industries.

The immediate improvements allow organisations:

• To analyse data more comprehensively (e.g. in the areas of risk management and customer profiling/segmentation) to provide greater insight / understanding
• To make data available more quickly to facilitate decision making, especially for exceptional cases (e.g. when not meeting KPIs)

Other side benefits derived from implementing such projects are:

• Data gaps: It can identify insufficient or unavailable data for making better decisions.
• Process gaps: It can identify business processes that need to be improved, e.g. manual processes that need to be fine-tuned or automated.
• System gaps: It can identify areas where the system needs to be improved e.g. improvement to existing system functions, or a new system needs to be put in place.

With such gaps and their relationship to the values of decisions, an organisation is able to prioritized resources to address those gaps over time.

Improve its table/data editor to allow easier ways to pull multiple data from multiple sources and associate them to establish a complete business data model.

Consider providing more features that allow the decision-making process of analysing different data at different levels to be captured. Maybe a decision-making flow/process editor for Qlik sheets and objects at the presentation layer.

I have used QlikView for approximately five years.

You can encounter deployment issues if you do not follow good / recommended “best practices”. Such issues can always be resolved through better design of the implemented solution.

By adhering to good practices, deployment, stability and scalability should not be an issue.

Technical support is average.

Initial setup is straightforward and much easier than other traditional BI software.

We are a Qlik implementation partner. We implement Qlik solutions for customers.

Our customers’ ROI is typically within 1-3 years, depending on the size and complexity of implementations.

Initial pricing/licensing of QlikView and Qlik Sense are competitive to the market. However, as the number of users grows, it could be costly.

You need to understand well the users’ decision-making process, the data requirements and the actions users want to take. It is OK to start a Qlik project without complete data available.

The associative engine and feature-rich expression scripts are the most valuable features of this product.

Easy, low-TCO solution to consolidate and visualise data for analysis and reporting purposes.

It provides better visibility of the company's position and its operations.

I would like to see more visualisation objects features.

I have used QlikView for more than a year.

I encountered minimal deployment issues.

Technical support is excellent.

I have experience with other similar visualizers, but QV offers a better experience in terms of ETL development.

Initial setup was straightforward, with a simple, easy interface. We had a simple setup anyway, not much complexity. We were able to get QV up and running in a very short turnaround time.

It was implemented in-house assisted by a lean vendor advisory team.

Data mining and consolidation are the products most valuable features to me.

I was using this to track KPI’s on my outsourced end user support (ticketing, resolution & time it takes to resolve). This forced my contractor to deliver because QlikView provides an analysis of the issues as they appeared.

I would like to see improvements to scheduled reporting and the capability to email the user.

I have used this solution for over four years.

I was using the cloud-based solution, so I didn’t have any issues.

Technical support was super, can't complain.

I had used other solutions, but they didn’t give me the kind of reporting & analysis I got from QlikView.

Set up was easy. Being technical, I found it easy and straightforward.

For our installation, we used the vendor. However, for my peace of mind and understanding, I was involved throughout the process.

ROI was not a consideration for me, though I would would say it was a great tool I would have equally gone for, even if it involved doing the ROI.

My use was more about service measurement & improvement.

The dynamic interactive dashboard is the most valuable feature of the product to me.

Lots of scripting used to be required to build high quality dashboards.

This cannot be considered a self-service product. It requires IT support.

I have used QlikView for one year.

This is quite a stable product, but very huge data loads must be complemented by good hardware. Otherwise, there could be performance issues.

Technical support is OK.

The only reason we chose this product is its dynamic interactive dashboard. It works well on iPad. We liked the product, as compared to MS BI.

Initial setup is quite straightforward, but it requires good hardware for high data loads.

An in-house team and a vendor team collaborated on the implementation.

It is quite expensive. There are two types of licenses: Named User licenses and Doc CAL licenses.

You need to have good scripting skills.

• Load script engine (or "ETL" ability)
• Connectivity integration options
• Data visualizations / dashboarding

As a start-up, projects need to move fast and this product has enabled us to have data solutions ready when the business needs it.

• Better compatibility with Qlik Sense
• Better support for non-Microsoft platforms
• SFTP support in the load script
• More built-in connectors

I have used it for three years.

We wanted to upgrade to version 12 but had two models that were not reloading as expected and had to revert.

Technical support is good.

We chose this product because we needed to connect to the source system and report directly from it.

It was already established when I started.

Initial setup was straight forward. The only challenge is maintaining a custom user directory by hand, because of a lack of Active Directory in the organization.

Now we do everything in house. At the very beginning, before I started, we had vendor support.

ROI is tricky to measure but I'll give some examples:

• Finance can now do month-end statements in one day instead of seven.
• We can determine if a new product in a new market will be profitable within weeks of launching a pilot.
• Engineering is free from having to run database queries to answer business questions.

You need at least as much RAM on your server as the largest database table you will read, and it can't be a virtual installation.

• The in-memory engine is really powerful, making it possible to deal with huge data records on the fly (more than 400 million in a table). I have built data models with over 1 billion records and the performance is good.
• With in-memory calculations at the UI (on the fly), it is possible to build charts, tables, etc. directly on the user interface (UI).
• Cubes are built on the UI. No need to pre-aggregate data, but it is of course possible to do that in the script (which I would not recommend) or better deliver data as SQL-View.
• Scripting possibilities to build complex applications and functionality.
• Web integration capabilities, for ex. you can include JScript Objects or R for better visualization.

We are service providers and built applications for our customers, not for us. Our customers are able to evaluate their marketing campaigns at the aggregated and customer levels. They can use micro-segmentation to select the leads.

We actually use QlikView, which does not allow easy-to-use framework management. There is a deployment framework, which I do not find easy to use and somehow not stable. I hope QlikView can improve this.

I have been using this solution for 3.5 years now.

There is no general rule, but we use the deployment framework, which allows us to produce a QV application user with four different levels of deployment:

• One level for the extraction of the data (1 to 1)
• In the second level, we get the original tables and based on the user requirements, build the data model and make the necessary transformations.
• In the third level, we get an intermediary state of the data model to be loaded in the end-user application.
• The fourth level contains the end-user application. We do a “binary” load, which is a command line in the QlikView script that allows us to copy 1-1 to the application we are copying from, in this case, from the third level. We have separate development from production and testing in a highly reachable environment (cluster environment).

It is stable, but of course stability depends on your IT infrastructure and deployment chosen.

Data model, data size, RAM size, hardware CPUs and UI expressions / charts, are strongly related. It is possible to scale QV without problems, but the issue is more complex than not having enough RAM. Complex expressions at the UI level, single threaded object calculations, complex data models, huge data size, etc., can alter the performance of the QV application and thus we might think we need to scale. There are many tools to measure QV performance and to try keep them at an optimal level. Otherwise, if everything else is fine, we need to increase RAM. Actually, we have 1 TB RAM on our production server.

Technical support is good, but could be improved.

Initial setup was straightforward. You need a server, install QlikView with its web server option and then you can start doing applications.

For more complex architectures (clustered, with two or more servers), you will probably need Qlik Tech support.

We contacted Qlik Tech directly for a cluster implementation (at my current company).

Pricing/licensing depends on your company size, the uses of QV, # of users, among others. Named CALs, at approx. 1.200 EUR (see the Qlik website), would be required if you have permanent users with write access to different applications, while Document CALs are good if you have users that will only see a document to perform their jobs. There is good and simple documentation explaining your best pricing / licensing model.

For my previous company I compared Tibco, QlikView, Tablaeu, and other tools, as indicated in the Gartner Quadrant. We did workshops with them, and were happy with QV because you can build something immediately. In the case of Tablaeu, you need a really well-established ETL and / or views. Otherwise, it is complicated for a normal user to build correct charts. Users have normally very little understanding of the data structure. Other tools need pre-aggregation and a long development process. With QV, it is possible to use views, pre-aggregated or raw data and you can still manipulate the data in the script, i.e. do ETL (see Deployment Framework).

1. Check your user and business requirements first and check if QV can help you solve your user / business needs.
2. If yes, check what are the potential uses of QV and describe the environment, company or unit size, # of users, # of applications, # of KPIs, and data volume. After this first check, you may be able to determine how big would your applications be, and thus estimate current and future RAM, necessary IT Infrastructure, # of servers, etc. I would talk to IT to see how to integrate QV into your IT environment. Many people start with an isolated QV implementation in their unit, which is fast, but then you have no single point of truth (this may discourage adoption because the user does not trust the data). But it depends on your goals.
3. Start working and promote user adoption, showing good functionality, fast implementation, and reliable data. QV can then become the main BI tool in the company.
4. Looking forward, QV can be extended in the use of mash-ups, Jscript extensions and analytics with R, so that you can build up in the future. Qlik Sense is a new Qlik Tech product, which offers many new possibilities.

QlikView's associative data model is the key feature of this application, which makes it superior amongst other competitors. It eliminates left, right, inner joins, and takes care of creating links between different tables.

Other valuable features are the Power of Gray, on-the-fly data cloud creation, and its ease of use and deployment.

With the Power of Gray, QlikView shows you what you are doing and what you are not doing.

New graph / chart objects need to be added.

I have used QlikView for the last four years.

Deployment with a big data cloud is a challenge so far.

Technical support is very good.

Initial setup was straightforward.

Before you start implementing it right on your computer, you have to design the data model on paper. Once you have an error-free data model on paper, you can finish the project earlier than planned.

Pricing and licensing depends upon the offer made by the vendor. However, QlikView ROI is extensively very high. We have seen it when we receive upsell requests from clients.

There are different tools in market, we have to differentiate between visualization and analytical tools , QlikView is analytical and descriptive tool.

Data visualization and the data modeler are the most valuable features of this product to me. I noticed that Qlik takes less time to set up data sources and enables us to integrate multiple tables. It is easier to manage variables with Qlik's data management.

As an insurer, we foresee that Qlik will improve reporting processes.

I predictive analysis is an area with room for improvement.

We will be starting implementation in August 2016.

Technical support is best in class.

We evaluated three other products. We chose this product because of its cost effectiveness, quality of services and advice.

Initial setup is straightforward. The vendor gave us a better understanding of the Qlik environment, data and dashboard development before moving to full training.

A vendor team implemented it and provided clear advice in writing.

We were provided useful advice with competitive pricing that supported our decision to purchase five licenses in the first phase of the project.

IT from some other companies have asked me, and I recommended that they use Qlik.

The most valuable feature of this product is quick and easy access to data by top management, in an elegant and colorful display that make is easy to visualize numbers.

We are able to provide top management with dashboards that connect different applications together, and gives them visibility and decision-making abilities that simple reports don't.

The management console is cumbersome to use for managing large numbers of users and documents.

I have used this solution for five years.

I did not really encounter any issues with deployment, stability or scalability.

Support and customer service are highly rated.

We evaluated this product against other BI products such as OBIEE and Cognos. We preferred QV because of its ease of use and fast deployment and development of dashboards.

Initial setup was straightforward. We just installed the Server Edition and configured it in no time.

We implemented it in-house. There are no specific skills needed, except basic knowledge of Windows.

We mainly use QV for providing dashboards to top management, as licensing is very expensive.

QlikView is a great product to get you up and running easily and quickly. However, it does not replace an enterprise reporting solution. It should be used for specific needs and would be too expensive and cumbersome to manage to deploy across the whole institution.

• 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.

We appreciate the different methods how data can be provided to a developer, designer and end users. Develop new reports from production databases to final reports without additional tools and
the high-performance loading data from database without any performance issues on the database environment. The loading performance of QlikView data container.

With the solutions of QlikTech, we are able to provide management with requested reports with proven data within a short time.

We can scale the user properly for the report environment in different and multiple ways.

Preparing actual daily reports without requiring additional manpower was the biggest benefit for our company.

We would like to provide our customers with reports in PDF or other popular formats that are not included in the publisher; additional licenses are required for the print and PDF tool. From my point of view, a reduced functionality for this should be included with Enterprise Server Edition or Publisher.

But so far, every new version includes new benefits for us.

We have used QlikView since 2010. That includes one year of testing QlikView Personal Edition for development and comparing the functions with our previous BI solution. We started using QlikView in production at the end of 2011.

We implemented different versions of QlikView within a few years, starting with version 8, Small Business Edition to Enterprise. We also moved to new hardware environment, but never had any issues. All versions we had in production were always stable. At the same time, we never used the first release of a new version for the server environment; the QlikView application has always been tested. Developing and deploying new reports are always tested in test environment before we publish. Scalability of reports should be considered separately.

Issues with the software itself are really rare; we just needed help implementing license keys after installation because direct internet access on the server was not available one time during setup. We always get help within a short / acceptable time. Normally, we just use the big user community for further help or information.

Before 2012, we used SAS and Crystal Reports for reporting and BI. When we started looking for other solution, we evaluated the new version of Crystal Reports, but there was no comparable alternative to QlikView.

A comprehensive concept for the initial setup is very important; there are various ways to implement the server infrastructure. If the concept was done properly, implementation might be complex but not difficult. We never had to contact QlikTech for additional support.

The documentation itself, user forum and several tech days was always helpful to start.

We implemented the whole environment without any additional support. Before we start working with the product, we organized in-house training from a vendor partner for developers and report designers based on our requirements.

My advice for implementation is to create a team made up of developers and IT department staff to set up the concept for test and production environments.

Training for IT and developers is available from the vendor, or if you organize in-house training from the vendor partner. Provisioning of data should be the responsibility of the IT department. You can also plan to have the vendor or vendor partner implement the product.

The vendor offers multiple possibilities for getting started with QlikView. It also depends upon how many reports you need for initial go-live. Starting with the Small Business Edition or Enterprise depends on the company size and the number of users who will work with QlikView.

The only important advice is to take enough time for the concept of the future environment.

That will make it easy to implement all needed add-ons with future changes.

Follow the vendor’s suggestions for scale responsibilities (IT, developer, designer and end user).

The Qlik user forum will be always helpful to find a solution.

The traditional BI tools are extremely limiting in the fact that they require very strict controls on the sources of data. This is understandable in very large corporates, but in a small- to medium-size business, where most supporting data sources are nothing more than an Excel spreadsheet, this is a pain. Therefore, my most valuable asset in QlikView is the ease with which any datasource can be integrated into the QlikView model for reporting.

The models created by QlikView have put critical information at the fingertips of management for decision-making processes. Our warehouse and distribution managers now have a view of the movement of stock, fulfilment of orders and can plan for demand more proactively. We produce our management sales dashboards daily and use the tool to integrate proof of delivery documents with sales orders.

I have several lower-level users who don’t need full functionality of the tool, but do need to access more than one model. In this regard, the licencing structure is limiting and costly for a user who is not using the analytical aspects of the tool. QlikView only offers full-user CALs (expensive) and document CALs (less expensive), but those licences only allow the user to access one model.

The business has been using this product for four years.

I did not encounter any deployment, stability or scalability issues.

Our implementation provider is very capable, but it is important to partner with a vendor who has industry, regional and technological capabilities, as this cuts down the time to develop customised requirements. Also, it is not necessary to limit yourself to one vendor and lots of freelancers are cost effective for specific requirements.

I looked at IBM Cognos, SAP BusinessObjects, and MicroStrategy. The main draw cards to QlikView was the cost and flexibility.

Initial setup was straightforward.

A team from the implementation provider did the installation and it was simple.

Our ROI is the ability to immediately take catalytic interventions with information at hand, implementing immediate savings from lost business and being able to put products to market more effectively.

In-depth analysis on the user roles using the tool should be done prior to implementation as non-managerial staff could probably use a shared licence scenario enabling lower licence count.

If possible, a site visit to other consumers of the tool often sheds a lot of light on work that can be done before implementation to overcome unnecessary problems and delays. For example, properly mapping financial processes, documenting and getting them signed off before a QlikView model is developed will save time and money in rework after the fact. Also forming a network of other users who are not related to the vendor is very valuable in getting unbiased advice.

It is quite versatile and reasonably cost effective.

• ETL functionality is hugely important, as data rarely are provided smooth and clean, even when the assumption is it has been cleaned beforehand. Plus, usually in BI, we need to create custom groupings, and being able to do that in script ad-hoc is very helpful
• Scripting for loads, with lots of functions, and insert script possibilities all provide extremely good flexibility for development.- Overall flexibility and ease of development is great for ad-hoc quick fixes, quick workarounds, which happen in BI
• Set-analysis function, unique for QV, is an awesome way to create subsets, literally under any chart/table/text box needed in a smart, fast way (replaces long expressions such as “if...then...“). It also allows you to control results, taking into consideration user clicking and selecting data.
• Associative model is super handy to just take an overview of data quality through visual associations (power of grey).
• Data governance is an extremely usable feature; there is no need for BI to build its own app, and it helps with licence monitoring.

With QV, literally all departments across the company have started “owning” data in terms of getting hands on data, knowledge about data, how it is built up, and the ability to slice and dice, add, expand, or decrease the size or granularity of their own reports.

This in turn has in general decreased the “fear” of touching applications on computer. With backups maintained by IT, people are given more freedom to try and change applications themselves.

Regex. Cleaning out data during script regex could be really handy.

Otherwise, I am having a hard time thinking of any other areas with room for improvement.

I have used QlikView 9 for two years, I am trained and certified on
QlikView 11, and I have used QlikView 12 for half a year.

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

I have not had direct contact. Currently (with Qlik Sense), I am working with Qlik local partners, not directly.

Before QlikView, Excel was used across the company. At the same time, we had SAS Web Reporting Studio provided by my company’s headquarters, which was very far from even being considered to be used for anything beyond just comparing total sales numbers if the QlikView reports were in line.

I remember it being set up with the first production app running in three days. So, initial setup was straightforward.

Implementation was done in-house.

During the selection of the local BI tool, the choice was between IBM Cognos and QlikView. We were naturally showcasing to management how easy it is to use the UI, and the latter one was chosen.

I think it is the best BI product out there, competing only with its own “brother” Qlik Sense. (While the latter is not that mature yet, it is definitely growing in power extremely fast.)

QlikView is a good choice!

Completeness in functionality and user friendliness are the product’s most valuable features.

Efficient reporting and analysis saves time and improves business insight.

I would like to see a modernised user interface.

I have used QlikView for seven years.

I did not encounter any issues with deployment, stability or scalability. It's a well-proven mature product.

I rate technical support 10/10.

We used MS Analysis Server & MS Reporting Services for some years and compared to Qlik products, it was inflexible, old-fashioned and slow.

Initial setup was straightforward as an all-in-one product, compared to Microsoft’s product stack.

An in-house team implemented it.

In the starter pack, you get a lot and the ROI is definitely less than a year.

I would recommend it to anyone who is looking for an online reporting and analysis BI product. Not to use only as a report generator; it's far more useful than that.

I do like the richness of details you can set up. It really allows you to set up a dashboard with pinpoint accuracy.

It was the first BI tool on the customer's site. It requires quite high skills at the entry level, so it was unused until I helped them with the initial steps.

The script engine for loading data needs a total overhaul. It is hard to use and counter-intuitive. It also blocks less-skilled users at the very beginning.

I’ve used it for about a year with one of my customers.

In general, the solution is a little problematic in terms of scalability, as everything is stored in RAM. For more complicated analysis for many users, the memory consumption is very high and requires a lot of investment in hardware.

It was already deployed when I start using it. My customer said they relied heavily on vendor.

Be very careful when scoping the market. It is a good tool, but quite heavy on skills and hardware requirements.

• Instant loading of huge amount of data and immediate display of relationship (both correlation and absence of correlation) between data
• RAD development methodology adoption for QlikView projects
• Set analysis function for simultaneous display of alternative aggregation sets

The backend (scripting) needs improvement to be more like a real ETL BI tool. The script editor is, in my opinion, no more than a basic scripting editor with too-limited debugging features.

I have been using it for five years (still today).

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

Technical support is very good.

The initial setup was straightforward.

We usually implement in-house, but we also rely on external resources.

We are currently using two different BI solutions for our customers: Business Objects and QlikView.

QlikView lets our customers develop data analysis projects independently with a little initial training.

Only a recommendation in order to assure the growth of a project with minimum impact on the previous deployed portion: As much as possible, try to solve data complexity on the backend side (where the logic is easily documentable), rather than in the front-end using only analytic functions.

• The way data is loaded, transformed and stored in one single file with a high compression rate
• The development flexibility allowing almost any type of relationship between data from disparate sources

Uniformization of KPIs across all departments brings efficacy and effectiveness to coworkers in problem solving.

Performance at front-end level could improve but usually there is a workaround - by reducing application size, splitting applications or the way the UI is presented - without affecting user experience.

I have used it for two years.

There can be issues in terms of stability during usage peeks. In these situations, the server can experience short down times. Again, many of these situations can be prevented by using the best development methodologies.

Technical support is very good. They are always available on providing guidelines.

There are other data visualization tools similar to QlikView. Spotfire, for example, has incredible UI possibilities, but I think QlikView is very ahead in the competition in terms of solution flexibility.

QlikView setup is very straightforward, only requiring server parameterization in terms of ODBC and the QlikView Server. It is not complex when compared to similar products.

It was implemented by an in-house team; some persons on the team had previous experience with QlikView. The learning curve is very quick, but the best practices provided by Qlik must be followed from the beginning of implementing the QlikView architecture.

Due to the quick development of QlikView applications, best practices cannot be disregarded. (For example, load only fields/tables that users need to be available in the application’s layout. When the number of applications starts to increase, this can seriously affect user.

I use QlikView to combine data from different sources in the absence of an EDW and build our analytical dashboards.

It allowed us to improve our analytical abilities, and KPI and data presentation, in addition to creating easily accessible what-if scenarios for decision making.

The security features in QlikView are not yet mature: very complex to define permissions in a dashboard (based on data/sheets).

We have been using QlikView for the past five years.

QlikView relies heavily on memory. It requires good servers and continuous upgrades and maintenance for sustaining good performance.

Technical support is good.

Most solutions like SAS, Tableau and others require a fully-fledged data warehouse (EDW), and IT support and intervention at all times for creating dashboards. QlikView is flexible and allows users to create their own reports in a relatively short time.

The initial setup was supported by the company and was not very complex.

Licensing in QlikView is a bit expensive.

I would recommend the QlikView tool for its flexibility and good data visualization and presentation.

Data exploration and in-memory capabilities: It has an associative data exploration feature and can handle one hundred million lines of data and provide good performance.

N/A. We are consultants.

Qlik has launched another product, Qlik Sense to improve ease of use for the end user. The product lacks PDF exporting, mapping – which costs extra - and reporting features. Also, it turns the data into QVD format that is not accessible by other software.

We have been using QlikView for five years. We have been a partner for five years as well. We have successfully completed seven QlikView projects.

I did not encounter any issues with deployment, stability or scalability. It is quite easy to install, configure and deploy.

QlikView has a very good developer community where you can find support from the other developers.

We usually position this product for departmental and fast-win solutions. When you’re an expert in this product, it’s quite easy to develop well-functioning and complex dashboards.

Initial setup was quite easy.

QlikView has CAL and Document CAL licencing. It’s quite cost-effective when lots of end users use several reports like once a month.

If you plan to develop dashboards and want the end users to further develop the dashboards, it requires some IT skills. If the end users should develop their own reports, Qlik Sense should be chosen.

Qlik's data modelling is very powerful and allows for easy integration of data from multiple sources. The in-memory associative engine is very powerful and provides quick answers to questions that arise when a user is exploring their data.

QlikView provides rapid insight that takes significantly longer to reach when using some other traditional BI tools.

I would like to see the desktop user interface updated. Some of the dialogs in the product look quite dated. I would also like to see the responsive UI design features from Qlik Sense make their way into QlikView.

On the analysis side, I would like to see tighter integration with R, or perhaps some built-in machine learning algorithms.

I would also like to see Qlik products made available on other platforms such as Linux and OS X.

I have used this solution for 8+ years.

QlikView is an in-memory product, so large dashboards place a significant load on a server's memory. This needs to be carefully considered when sizing your environment.

I have used a number of competing products such as Cognos, Tableau, Power BI and SAP BusinessObjects.

QlikView development projects are rapid and the product itself is very flexible and reliable.

Initial setup of QlikView tends to be fairly straightforward, though when setting up additional features such as clustering and publisher features, this can get a little complex.

I have implemented the solution both with vendor teams and in-house. In a previous job, I worked with a vendor team, and have worked for a partner and provided implementation support for clients.

I would advise new Qlik customers to seek out a reliable Qlik partner to help with implementation.

I would advise you to seek out a local Qlik partner. They will be able to support your training and consulting needs and provide guidance regarding best practice for your implementation.

QlikView has some superb, unique features but the desktop edition suffers from having a rather tired user interface. Default chart settings can often result in unattractive dashboards, which require significant adjustment in order to conform to best practice. These UI shortcomings have however been addressed in Qlik Sense.

The data model and the visualization are the most valuable features of the product. The data model helps my organization to recognize and identify the problem of our clients’ data. The visualization helps us to deploy an easy-to-understand solution to the client and they are able to explore the data by themselves.

We actually help the client to deploy and design the solution. It helps us to understand their problems better and provide a more intuitive solution. Plus, after the deployment, the client is able to explore and maintain the application without any further charges on the software itself.

The visualization charts. I believe they are working on that because Qlik Sense has released a few versions in which the charts are a lot better than QlikView.

And the interface. QlikView is mainly defined as a guided analytics tool, which requires experienced users to help with the development. In the future, it should move forward on self-service (the core value of Qlik Sense), which is the trend on the business intelligence development. So I think they will have some big changes coming.

I have been using for about one year.

I haven’t come across any fatal issues with deployment, stability or scalability so far. However, as the data volume increased, the skills of optimizing the tool need to be more advanced.

Technical support are quite helpful. We are a Qlik partner and they are willing to help out with issues. Sometimes, they ask for feedback when a new version is released.

It’s straightforward and very detailed documentation is available; just follow the instruction prompts when you install the software.

I also tried Tableau. I believe they are targeting a different market, if you compare Tableau with QlikView. The better comparison will be Tableau to Qlik Sense, which is beyond the scope of this review. The reason we selected QlikView is its relatively comprehensive functionality.

• Connect to multiple sources of data without needing ETL prior to load
• Ability to create complex data joins within the script
• ETL features
• Ability to do complex customization in the design and data representation (set analysis)
• Associative search capabilities

• Scalability
• Live connections
• Responsive design

I have been using QlikView for four years.

Customer service and technical support are very good.

Among Tableau, QlikView, and Qlik Sense, I prefer QlikView, due to its higher customization capabilities, its associative nature, and its ETL features.

Initial setup simplicity or complexity depends on the project and the systems already in place. As for the tool itself, initial setup is straightforward.

I have implemented it in-house and with a vendor team. Business needs need to be fully understood and documented. Most of the issues have always been data related. The development team and the business HAVE to get a full understanding of what the data is, where it is stored, and how it is stored. BUSINESS RULES and a DATA DICTIONARY are a must.

Standardization in design/development is crucial. FULL communication and documentation with EVERYONE is needed. I don’t know how much time has been lost or efforts duplicated because of a lack of all this.

• Intuitive data insights and standard reporting.
• It runs in-memory so you can increase the speed by increasing RAM, depending on your budget.
• It has its own ETL tool, QlikView Connector.

It gives intuitive data insights to improve and optimize our global supply chain (help drive and build strategy to improve on-time delivery, reduce quality and damage returns, etc.), with a few simple clicks to drill down to the details (down to the SKU level and call centre conversation details with customers). The dashboard gives management a holistic picture on our important KPIs.

• Enhance predictive analytics and big data; this is the future trend.
• Simpler, cleaner charts and visualization (easier user acceptance)
• Formatting and repositioning the menu/charts takes a bit long. It does not have drag-and-drop capability like Tableau does.

I have been using QlikView for 2.5 years.

There’s no version control, which means you can't roll back to earlier versions once overwritten/published.

I rate technical support 6/10.

I also evaluated MS BI and tableau. Compared with MS BI, I find Tableau and QlikView have stronger visualization; intuitive data insights; less development lead time - MS BI requires creating OLAP cubes, which takes more time; clearer and simpler charts; and intuitive data mapping/insights.

Initial setup was straightforward.

We implemented it in-house. QlikView is running in memory, so it depends on your organization to achieve the balance between cost of server RAM and performance. Besides, the data quality and accuracy is very important, no matter what powerful visualization tools are used.

Tableau seems to have easier user acceptance than QlikView because of the simpler charts and big data integration, increasing the possibility of helping an organization transform from reactive analysis to predictive analysis.

Server versions are not cheap and pretty similar for both Tableau and QlikView in terms of price. I don't see a big difference; it really depends on your organization's need.

If you have more developers/technical people and want to do more standard reporting without Hadoop, go for QlikView; if you have more business users with some SQL knowledge and would like to do predictive analytics, and integration with big data platform Hadoop, go for Tableau.

It allows our company to view all of our data in a single solution. It is easy to use, even for novice users.

The product has reduced the number of reports that were previously constructed manually by users. It also allowed us to prepare a single report using a common data source for all users.

In QlikView 11, there is a password for the section of code, but there is no user management with a password that allows access to data when opening the file.

I would like the data loading and programming to be made easier.

I have been using it for five years. Currently we're using v11.20 and testing v12.

The product installed at the time did not present operational problems or stability issues.

The consultant company that sold us the product provides us with follow-up service. At the moment, we are satisfied.

I used BOARD at another company. I have found QlikView to be better.

The initial setup was very simple and in a few days, we were able to begin operating with the data available.

We developed the solution partly in-house and partly with the supplier. We took responsibility for the preparation of the database, retrieving information from the management system and preparing it in a suitable format, leaving the supplier responsible for the implementation of the loading from this database and reporting.

We are happy with the product. With regard to the license fee, for a customer, it is always better to pay less.

QlikView Desktop Enterprise allows us to build dashboard visualizations in a fashionable way and allows us to make quick business decisions all over the enterprise.

The improvement was much more related to be able to link different data sources to the same visualization. Now users have access to a one-stop shop for their data queries.

I believe that improved analysis prediction capability would be more than welcome in QlikView. If we could simulate scenarios in a more intuitive way that would be a nice-to-have feature.

Besides the fact it’s quite a useful tool for data visualization, the final user interface is not that intuitive. That might be the idea with Qlik Sense, which we haven’t had an opportunity to experience yet.

Prepare your data warehouse platform. The more time you spend on DW development, the more your users will be able to take advantage of the data analysis.

Data integration and visual drill-downs are excellent.

I work for a consultancy and develop projects for clients. Our clients have definitely got benefits with the use of QlikView with accessibility of their business metrics in an interactive form on their smartphones. Also, QlikView can compress and store data in its own format, which makes it faster after data loading.

• Version changes should be made fully compatible with older versions.
• Advanced analytic capabilities of model building using regression or time-series analysis should also be added in the product.

Client requirements should be clearly understood and limitations of the product should be communicated to clients before making any commitments. Often projects are jeopardized due to poor communication and unclear expectations.

There are two reasons for my rating. First, the interactivity options are limited and, second, modelling options are not available. Also, we faced challenges with version changes and in integrating it with geographical information systems.

Fast development, support for QVD format files, and business discovery are the most valuable features of this product to me.

Before we started using QlikView, we needed to put or clean our data in four steps. Now, we just connect the database, clean it and show the information.

In the next version/release, I'd like to see mashup possibilities and real-time connections.

I have used QlikView for five years, and Qlik Sense for two years.

I encounter deployment issues but it depends on how you develop it and for what are you using this tool.

Technical support provides high-level service.

Initial setup is straightforward; you just install and use.

When implementing through a vendor, be careful with your environment.

This product pays for itself fast.

Try it. You can use just one tool for most of your connections. It's easy to maintain and you can focus on data and decisions.

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.

The best features of QlikView are:

• The fast and easy process of extracting data from multiple sources (DB), although having duplicate data in the source files creates a mess.
• The intuitive way of creating dashboards for finance, sales, BPM, etc.
• The display and drill-down access to detailed information, graphic interfaces are easy to create and dynamic using just one pivot table.
• The easy way to grant access to all the data or just bits of it to specific users.
• The capability of QV to handle .pdf files.

As an example, today we have our budget information from different areas in one summary page. Numbers are updated fast and easy in the web browser. This has given crystal clear info for all the users that have access to the model. Hard data and dynamic graphs give a clearer and accurate view of the data. Filtering saves a lot of time when doing presentations to the top executives of the company; any question is answered in real time with just a few clicks.

I would like to perhaps be able to have preloaded and editable examples of models created by QV experts that can be customized for our specific needs, instead of starting from scratch anything we need to work on.

I work an electric utility in Mexico, therefore we build QV models and dashboards specific to our industry (electricity, gas, nuclear generation, asset management, executive reporting and such). 

Right now, we have to build our models from scratch, if we could have access to prebuilt models for our specific industry and line of business it would be very useful and time saving. 

It’s important to understand that the quality of the final data will have a direct relationship to the source of information. You can really apply here the phrase "Garbage in-Garbage out". Because once QV is up and running, almost everyone will turn to the dashboards as THE source of information, it’s imperative to be sure the source of data is flawless.

It’s a great BI tool to convert raw data coming from several different sources into a dashboard full of in-depth knowledge, to do proper information analysis and make accurate decisions for the company.

Usability, usability, usability: It is easy for developers and for end users.

We have cut Fire Department 911 response time 8-30 seconds.

We have improved the timeliness, accuracy, and consistency of reporting.

Unmetered water reports (e.g. fire hydrants, FDCs in commercial buildings)

Wage verification requests

Performance metrics

We have improved processes and increased compliance of firefighter training and certification, ensuring that firefighters are properly trained (“a trained firefighter is an effective firefighter”), expensive training courses no longer have empty seats, and we have improved our performance on training/certification audits from our regulatory agency.

We have engaged line managers on tracking and monitoring of program and operational budgets, leading to better oversight of the taxpayer dollar.

The QlikView management console could have better interfaces for managing security. Right now, it is hard to tell “who has access to exactly what apps?”

Better out-of-the box governance features, to allow analysis of application architecture, optimization of scripts, identification of unused fields/data.

Current GIS interfaces (e.g. with ESRI) are through partners, and are acceptable, but could be easier to implement, more streamlined interface between the two.

I have used this solution since 2008.

No issues at all. This application requires very little care and feeding. Cannot speak to big data scaling, our largest data sets are in the 1TB range — but no problems noted at that level.

Customer and technical support are fine. Account manager deals well with the added layers of demand that come from being a government client — purchasing is always more complicated.

Like everyone, we used Excel and Access. We tried using the enterprise MicroStrategy and both developers and users rejected it as too much effort, not intuitive compared to QlikView.

Technically, initial setup was very simple. The hardest part was getting visualization requirements form unsophisticated users who were not used to any sort of reporting on their processes.

We did it in-house, with one week of one vendor person assisting. (The four apps he helped us put together, we ended up redesigning altogether once we had a chance to use them and redefined requirements.)

Advice: Keep it simple. We know of similar organizations that used third-party implements, who created apps that were complicated to support and use, and consequently those implementations were not entirely successful. In at least once case, they abandoned the product (and haven’t done anything else that I’m aware of).

Qlik has a reputation for being expensive, but our TCO - compared to two other BI products in our organization (MicroStrategy and Cognos) is way, way cheaper. We didn’t have to pay for consultants or any professional services. The more we let our business managers design and develop their apps, the happier they are.

Keep it simple, involve the team (prototype with them - don’t throw a fancy app over the wall at the end users and expect them to actually engage), do POCs before you decide which BI system you will adopt.

QlikView’s Associative Data Model allow business users to easily create data models.

QlikView’s in-memory technology offers lightning-fast drill-down and drill-through capabilities.

The ability to apply row-based security provides the flexibility to deploy a single application and restrict access to sensitive data according to role.

We are busy rolling out QlikView as a self-service BI tool. The business is delighted with the capabilities they have without the usual restrictions they encountered working through the traditional IT channels.

• Robust Version Control integration, limited in current versions
• Automated deployment between DEV/UAT/PROD environments, currently these are manual file-based operations
• More descriptive system metrics and lower-level diagnostic and performance metrics at the application level

Deployment is easy and straightforward, even for non-technical resources.

Stability is largely linked to the infrastructure and requirements. QlikView SA has provided extensive guidance on deploying suitable hardware to support our environment.

Scalability depends on the environment and requirements. If you have large data sets, due to the in-memory nature of QlikView, the hardware needs to support your requirements.

I rate technical support 10/10, excellent. Qlik as well as our local QlikView Partner, QlikView SA, provides extremely good service and support.

There is also an extremely large and active online community.

We evaluated IBM Cognos and SAP BusinessObjects. We chose QlikView because of its online community, extensibility and support, and large demand from business.

Initial setup was straightforward, but consideration needs to be taken when procuring the hardware.

Implementation was a combination of in-house and vendor. Take the time to understand the underlying architecture and deployment setup to later be able to troubleshoot the environments.

We realised instant value through data discovery not previously possible with traditional BI.

Consolidating six disparate instances into a single group instance has improved our ROI immensely.

Care should be taken to purchase the right type of licensing blend for the environment.

Take time to understand the different license types, the requirements from users, usage model, etc., before deciding on licenses.

Potentially get some demo licenses before purchasing.

Happy Qlikking!

Take the time to understand the data, and develop solid data models. This will ensure good performance and a great user experience.

Just because QlikView can do it, doesn’t mean it should. (There is still a place for traditional BI, databases and ETL/ELT.)

Develop fit-for-purpose applications.