Qlik Community

New to QlikView

Discussion board where members can get started with QlikView.

Announcements
Make your voice heard! Participate in the 2020 Wisdom of Crowds® Survey. BEGIN SURVEY
Highlighted
prachi91
Contributor III

Difference between QlikView and Qliksense

Difference between QlikView and Qliksense ?How they differ from each other? and their advantage & disadvantage ..

Thank you..

10 Replies
Highlighted
devarasu07
Honored Contributor II

Re: Difference between QlikView and Qliksense

Hi Prachi,

a) Qlikview is for Guided Analytics and  Qlik Sense is for Self-Service Data Discovery

b) both product using same engine

C) geo analytics (map visualization ) qlik sense is better than qlikview

d) Qlik sense have nice feature data storytelling which don't have in qlikview (this feature very useful presentation point of view)

e) Data loading in QlikSense is faster than qlikview

for more refer,

What is difference between Qlik Sense & QV Desktop client?

QlikView and Qlik Sense

Hope this helps you

Regards,

Deva

Highlighted

Re: Difference between QlikView and Qliksense

Highlighted
beck_bakytbek
Honored Contributor

Re: Difference between QlikView and Qliksense

Highlighted
prachi91
Contributor III

Re: Difference between QlikView and Qliksense

if qliksense is better than qlikview then why qlikview used in market.

Highlighted
beck_bakytbek
Honored Contributor

Re: Difference between QlikView and Qliksense

Prachit, the both software are good, all depends on you business environment

sohailansari201
Contributor

Re: Difference between QlikView and Qliksense

That's a good and evolving question. I bet we come across this question by our clients and users quite frequently. There are many answers available on the Internet but then there are real life practical answers that we learn with our experience in the field. I will try to summarize this difference with my personal experience.

According to Henric Cronström on community:

QlikView is a tool for situations where you want prepared business applications, i.e. applications created by developers who put a lot of thought into the data model, the layout, the charts and the formulae; and deliver the applications to end-users who consume the applications. We call this Guided Analytics. The end-user has total freedom to explore data, select, drill down and navigate in the information, and can this way discover both questions and answers in the data. The end-user is however limited when it comes to creating new visualizations. This type of situation will without doubt be common for many, many years to come.

My practical learning points about QlikView:

  • Organizations need to invest in HR expertise for QlikView development
  • Organizations need to invest in either in-house or hosted/rented QlikView infrastructure.
  • Not available in cloud.
  • Licensing is somewhat complicated and a bit expensive in my opinion.
  • Easy to use development interface.
  • Has some APIs available to integrate QlikView with your existing application and other QV management services.
  • The QlikView developer usually goes horizontal across all functional areas of an organization to collect data, bring it at a single place and design a data model for Qlik to consume. (Can leverage an existing ETL process and/or Data warehouse as well)
  • Many data connectors available to connect with a variety of data sources.
  • The QlikView dashboard development process works pretty much like any other software development methodology but I have mostly witnessed Agile methodology.
  • The QlikView dashboard building time is usually much more faster compare to any other type of software development.
  • The end user receives the ready to use product and immediately get the results required for B.I. Analysis.
  • In this case, the "Self Service" B.I. plays a small role. (Requires Power users/trained users)
  • The in-memory associative data model is amazing and beyond comparison.
  • Once you model the data properly, it can be used for QlikSense as well.
  • Offers much more control to developers over design and control of the visualizations.
  • Has C++ and C# in its roots
  • Mobile friendly with little effort
  • Mobile App available
  • Allows external branded reporting using it's tool called NPrinting.
  • Some pre-build extensions are available to use. However, you can also build your own extensions
  • Both QlikView and QlikSense environment can exist side by side.

Again as per Henric Cronström on community:

QlikSense is a tool for situations where you don’t want to pre-can so much. Instead you want the user to have the freedom to create a layout of his own and in it, new visualizations; charts that the developer couldn’t imagine that the user wants to see. You want Self-service data discovery, which means a much more active, modern, engaged user. In addition, Qlik Sense is much easier to use when you have a touch screen, and is adaptive to different screen sizes and form factors. On the whole, Qlik Sense is a much more modern tool.

My practical learning points about QlikSense:

  • QlikSense was introduced mainly with the idea of providing "freedom" to the end user to perform "Self Service' B.I. on their data. You give a data set (mostly Excel sheet) to end user and the user should be able to import and start making some visualizations and dashboard on its own. It's that simple. You can say it's Excel on steroids.
  • Does that mean you do not need QlikSense expert developers? No, the end user is mostly non-technical and does not know the in and out of data modeling or how to write efficient KPI formulas. For a small set of data, an end user can probably find their answers by doing self-service B.I. But when it comes to multitude of data sets, their size, sources, procurement, relationships, creating schemas, facts/measures, optimization, set analysis, speed, cross functional data, security and many other factors, you again see the need to bring in a QlikSense expert who can again provide you some "Guided Analytics" on this "Self Service" tool.
  • Organizations usually want to perform data analysis across their entire sets of data to find the patterns, trends & cross relationships. If every manager starts doing their own analysis there is a very high chance that they will be building their own B.I data sources and most likely will be coming up with different numbers for the same KPIs. And we know that management hate to come to this point. Therefore, bringing in experts make total sense in order to march towards single source of truth for the company.
  • In my opinion, the "Self Service" tag with QlikSense is mostly because to show it's simplicity to use. But as you start working with it, you will soon realize that you can make most use of it by putting an expert to it.
  • Many data connectors available to connect with a variety of data sources.
  • Easy drag and drop interface.
  • Licensing is simpler as compare to QlikView
  • Cloud option is available; therefore infrastructure cost can be minimized.
  • Uses the same power of in-memory associative data model.
  • The Control offered to developers over design and control of the visualizations is not as good as QlikView. This is good for a simple end user as they do not like too much customization but it gives frustration to the developers specially who are coming from QV background.
  • Many supporting APIs are available for developers for integration and other purposes.
  • Has Javascript and HTML5 in its roots
  • Highly mobile friendly
  • Mobile App available
  • Allows external branded reporting using it's tool called NPrinting.
  • A lot of third party extension are available to use. However, the problem I see with using extensions is the maintenance. As you upgrade QlikSense you got to be careful about extensions support for the new version. Many extension developers made them as their hobby, therefore support can become an issue for these kind of extensions. However, you can also build your own extensions if you want to go that route.
  • QlikSense is catching up fast with QlikView features and even beyond. It is improving with every new release. I believe there are couple of releases every year.
  • Both QlikView and QlikSense environment can exist side by side.
  • I have a feeling that Qlik as a company is focusing more on QlikSense vs QlikView (again this is just my opinion)

Please feel free to correct/update any of these observations.

Highlighted
nazneen1
New Contributor

Re: Difference between QlikView and Qliksense

Hi Sohail,

You have shared nice information. Thanks.

Highlighted
MVP & Luminary
MVP & Luminary

Re: Difference between QlikView and Qliksense

Just to add to this thread, it's not just a case of QlikView vs. Qlik Sense, there is also the question of which version of Sense is the right one to go for.

This blog post explains the differences between the different versions on offer:

https://www.quickintelligence.co.uk/qlik-sense-versions/

Steve

Highlighted
josephfallon
New Contributor

Re: Difference between QlikView and Qliksense

"Both QlikView and QlikSense environment can exist side by side."

You can't run the main services together on the same server though, right ?