What's the difference between Qlik Sense and Qlik View?

admin

QlikView and Qlik Sense are two different products with difference purposes.  QlikView is for guided analytics; Qlik Sense is for self-service visualizations

Qlik Sense is transforming from QlikView towards achieving goals of Self service BI.

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

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

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.
  

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)

  Qlik Sense不仅仅可以认为是QlikView的一个新版本，两者之间虽然有很多相似之处，但是他们之间还是存在着有着或多或少的差别。总体来说，两者有着不同的用户接口但是却共享着相同的分析引擎。这就意味着之前在QlikView当中使用的后台脚本和前端表达式几乎都适用于Qlik Sense，但是有一点小小的不同，Qlik Sense在抽取文件时不是总可以使用相对路径，而是使用库。两者都使用的是绿-灰-白的展示色调，使用相同的计算引擎，几乎相同的响应时间，因此你在设计数据模型的时候，两者并没有任何区别，你可以完全按照之前设计QlikView数据模型的思路去设计Qlik Sense的数据模型。之前提到过，两者还是有存在差别的，但是我们也没办法说哪一个更好一些，就好比做爸爸的永远不敢说自己的哪个孩子更聪明一些，因为他们各自有不同的优点。
      在QlikView中，开发者们将设计好的QV程序提供给用户使用，其实包括了数据建模，ETL处理，前端报表的展现样式等等。我们姑且称这种方式为引导性分析，用户可以自由的按照自己的需求来选取数据，钻取数据，很方便的发现问题和找到答案。但是问题在于用户不能非常方便的按照自己的需求创建新的报表，其实这也就是传统BI一直以IT驱动为中心所带来的问题。QlikTech公司曾提到过要将IT驱动转化为用户驱动，其实Qlik Sense主要就是针对这种需求所诞生的，在Qlik Sense中，用户可以按照自己的意愿创建可视化报表，实现自助式的分析，往往这些报表很可能都是开发者们所想不到的，并且Qlik Sense中的界面，控件以及任何设置都在向鼓励用户进行这种自助式的分析方向努力。除此之外，Qlik Sense更适合在各种触摸型的设备上使用，并可以自动的适应不同大小的屏幕，可以说Qlik Sense是一款非常时髦的BI分析工具。