What is the architecture of Qlikview

Difference between QlikView and Qlik Sense: an overview

This article describes the differences and similarities between the two analytics tools QlikView and Qlik Sense. Strengths and weaknesses are highlighted, use cases are compared, how the licensing differs and much more.

We also describe scenarios such as QlikView and Qlik Sense shared to protect existing investments. QlikView vs. Qlik Sense: What's the Difference?

QlikView (or actually "QuickView") was published in 1994 in version 1. Over the next few years, Qlik created the innovative area of ​​"Business Discovery" in the area of ​​business intelligence with the tool QlikView.


Even more information on the topic in the videos of our information workshop. Available immediately!


Various independent analysts picked up the trend from around the year 2000 and over time, terms such as "Data discovery"or"Data analyticsGartner, for example, has been calling the well-known "BI Magic Quadrant" "Magic Quadrant for Analytics and Business Intelligence Platforms" for some time.

In 2014 Qlik released the first version of Qlik Sense. In summary, QlikView has since been positioned as a tool for "Guided Analytics" and Qlik Sense for "Self Service & Visualization" use cases.


Qlik Sense is therefore not simply the successor to QlikView but a new, innovative generation of business intelligence.

What exactly are the differences and what are the similarities between QlikView and Qlik Sense?


In a nutshell: The commonality of both components is the central "In-memory engine", also known as" Qix-Engine ". Quasi the heart, the engine, the central unit.


For the development of Qlik Sense, this central component was cloned from QlikView, reused in Qlik Sense and further developed.


All other components have been developed from scratch in Qlik Sense: New server components, new APIs, new front end, new security rules and much more.


No time to read any further? Download our clear guide

QlikView Personal Edition vs. Qlik Sense Desktop

A desktop client is available for both tools for local installation on a PC or notebook.


But what are the similarities and how do they differ?

Let's start with the similarities:


Both tools are available free of charge.

Both QlikView and Qlik Sense offer all functions in the desktop version that are also available in the licensed version - apart from the server functions, of course.


Both tools can be switched on connect any data sources, all Transformation functions are available and ready-to-use Discovery and visualization apps of data create.


Both software components are intended for the same purpose: Get to know QlikView / Qlik Sense without obligation, without license expenses, without a complex implementation project.

If you like the solution, it will be licensed, if you don't like it, simply no longer use it.

The creation of apps is also the primary one difference both tools:


QlikView apps can only be used on the PC / notebook on which they were created.

Qlik Sense Apps can be used on any device by different users.


A furtherThe difference lies in the architecture or in technology:

The QlikView Desktop Client is required to create QlikView apps in a licensed environment: QlikView is a classic client / server application.


This is in contrast to Qlik Sense: This is a server-based architecture. The Qlik Sense Desktop Client is therefore no longer required in a licensed environment.


Releases: Several for Qlik Sense, one for QlikView per year

A new release for Qlik Sense will be made available every ten (10) weeks.

A release describes software versions that primarily contain new features, including functional tests and regression tests. Details on the Qlik Sense Release Management Policy can be found in this document.

An "incremental release" is planned for QlikView from November 2018 onwards.

In these releases, topics such as usability, flexibility and performance improvements are addressed in particular. In addition, the primary frameworks and platforms that interact with QlikView are taken into account. Details can be found in this article.

Data storage / qvd files

Both when using Qlik Sense and QlikView together, when switching to or starting with Qlik Sense, the question arises of how data is permanently stored in Qlik.


The short answer is: In both QlikView and Qlik Sense, data is stored in so-called Qvd files. These are XML-like containers that contain both the metadata and the data itself:


  • Qvd files created by QlikView can also be used by Qlik Sense reused become
  • Qvd files created by Qlik Sense can also be used by QlikView (as of February 2019)
--> But be careful: This point has to be verified with each new release of Qlik Sense or QlikView, since adjustments to the engine - with effects on the processing of qvd files - usually manifest themselves first in Qlik Sense and not always directly in QlikView be tightened.

Qlik Cloud / SaaS / Software as a Service

Qlik offers a classic cloud solution, i.e. software as a service, exclusively for Qlik Sense. QlikView is not part of the cloud strategy. If you are interested in obtaining Qlik Sense or QlikView from the cloud, please contact us, we will put together an attractive offer from the Heyde cloud.


The Heyde Cloud is based on FINMA-certified data centers with data storage in Switzerland.

Extensions / extensions

The standard scope of QlikView and Qlik Sense can be expanded as required with extensions. For example, the use of Qlik data directly in Excel (URL). Or changing / writing data back directly from Qlik.


However: The extension itself can only be used per platform. An extension that works in QlikView will not work in Qlik Sense due to the different technological platform. And vice versa.

These functions can be retrofitted in both QlikView and Qlik Sense. However, while one or the other technical hurdle has to be overcome in QlikView, extensions can be seamlessly integrated in Qlik Sense.


The Qlik Sense APIs are designed to implement integrations, i.e. to expand the standard range of functions as required. A selection of free extensions for both QlikView and Qlik Sense is available here: https://developer.qlik.com/garden.


Attention: Talk to your advisor before a productive use - not all extensions are supported / are suitable for productive use!

QIX engine: Common component in QlikView and Qlik Sense

The associative engine, QIX engine, is THE USP of Qlik: Instead of laboriously storing data in cubes (OLAP), the links in the associative engine can be created and used as required. This eliminates the limitations of OLAP technology and creates additional analysis options at the same time.


The QIX engine, the central component, is available for both QlikView and Qlik Sense.


Some background information on this: During the development of QlikView, the QIX engine was separated from QlikView version 11 and the other components (front end, server components, APIs, etc.) were developed in Qlik Sense version 1.0. After that, the QIX engine was brought to a new level within Qlik Sense.


This new level was in turn synchronized with QlikView, version 12.0.


The QIX engine is currently being further developed in Qlik Sense and will be updated in QlikView.

Library of measures and dimensions

Badly missed in QlikView: Predefined key figures & dimensions in Qlik Sense, ready for self service.


With the central library in Qlik Sense, it is possible to precalculate key figures and make them available to all self-service users as a drag & drop element.


While in QlikView this can only be partially solved and with detours via variables, the solution in Qlik Sense is well thought out. Not only can complex calculations be stored ready-made, but color codes and areas can also be defined depending on dimensions or values.


The added value is huge: Instead of defining the key figure separately in each visualization object, as in QlikView, the library provides a ready-to-use set. This eliminates ambiguities about calculations, different formulas for the same key figure, etc.


The creation of new evaluations takes place with it very dynamic but controllablet. The following images show the key figure library and how colors or color gradations are stored in the key figures. These definitions then apply to the entire application.


Pixel Perfect Apps / Dashboards

For the end user, the biggest differences between the two tools in the front end are immediately apparent: The bar or pie chart or even the table have a lot more modern and focused look and feel, even if the underlying core (the QIX engine) is the same.

The possibilities in QlikView allow the creation of a sophisticated and, if required, complex user interface: visualizations can be overlaid, shown or hidden based on conditions or placed exactly as desired.


Within the visualization, dozens of settings are available in QlikView to configure the behavior or appearance of a bar chart, for example. In other words: pixel perfect.

Pixel Perfect comes at the price of responsive design in QlikView and thus the dynamic resolution or arrangement depending on the end device: This point is solved in Qlik Senseby using an intelligent mechanism to ensure that the necessary and meaningful elements are always visible.


Regardless of the available resolution. However, the designer / developer can only influence to a limited extent when, for example, the break from horizontally adjacent visualization elements to vertically one below the other takes place.

Since the November 2018 release, setting options have also been available in Qlik Sense, which do not yet allow pixel perfect arrangements, but allow interventions in the intelligent mechanism.


However, it cannot (yet) be used to create pixel-perfect apps in Qlik Sense.

Feature comparison or different use cases

Often in companies that use QlikView, the Need for a functional comparison of QlikView and Qlik Sense.


Understandable at first glance, but hardly feasible in practice at the second glance: A list with hundreds, if not thousands of items would come about, which would only be of limited significance.


There are also many functions in both tools. However, they may behave very differently. However, in order to make a comparison anyway, the comparison of the different use cases is suitable.


The following list shows an overview of the degree of coverage per use case for Qlik Sense and QlikView.

Here, for example, the greatest differences can be seen in the areas of pixel perfect design, responsive design, self-service, authorizations or the cloud. These use cases support the comparison of Qlik Sense and QlikView.


Self Service in QlikView and Qlik Sense

The short version: Self-service in QlikView is possible, but there are hurdles involved.

These are particularly to be found in the increased need for training for end users.


Qlik Sense, on the other hand, has been equipped with the self-service concept since version 1.0. Whereby Qlik even went a step further than other self-service providers: In Qlik Sense it should be possible for every user to create their own evaluations or completely new apps, no matter how untrained they are.

This explains, among other things, the range of functions on the surface that were criticized in earlier versions of Qlik Sense.


Compared to QlikView, there are somewhat fewer setting options available in Qlik Sense, but the creation and, in particular, the operation of evaluations and apps are significantly less complex and therefore less time-consuming.


Qlik reduces the functional gaps with each release of Qlik Sense. At the same time, the brand is very careful not to make the individual setting options too complicated. A project that is not that easy to accomplish and that manifests itself in the time lag, among other things.



Permissions: Section Access also in Qlik Sense, plus security rules

With Section Access, requirements for the visibility of data in the app are implemented in QlikView and Qlik Sense.


This ensures, for example, that different cost center managers are only allowed to see data from their own cost center, but that the report / app only needs to be created and managed once.


In other words, an authorization concept at field level within a Qlik app.

In Qlik Sense, Section Access is supplemented and significantly expanded with so-called "Security Rules". While Section Access can only be used at field level, the Security Rules have access to all objects or "resources" in a Qlik instance.


In contrast to QlikView, this also allows the connection strings, i.e. the access to data sources, to be protected.

Or control the visibility of streams, apps or even worksheets in an app.


Whether someone is allowed to edit an app or not, whether or not someone has access to the QMC or to which areas in the QMC - everything is controlled with the security rules.


This means that very complex requirements for the visibility of Qlik resources can be implemented. The Security Rules are a new concept, actually a new engine reserved for Qlik Sense.

QlikView vs. Qlik Sense or QlikView AND Qlik Sense

Companies using QlikView are currently considering:

  1. Continue with QlikView?
  2. Switching to Qlik Sense?
  3. Or is it QlikView AND Qlik Sense?


1) Continue with QlikView

No steps necessary. Continue to rely on QlikView as a BI platform. Just like over 30,000 companies worldwide do.


2) Switching from QlikView to Qlik Sense

It is particularly important here Plan the transfer phase well.

A complete switchover, in a single step, can pose a number of challenges for both the internal organization and the end users. Therefore intrudes iterative approach on, with the following considerations:


  1. Implement new requirements primarily in Qlik Sense
  2. Start with the Replacement of a less complex QlikView appthat is used by few users. Learn and take the knowledge with you to replace the second QlikView app
  3. Take the end users by the hand and explain / train the transformation process
  4. Plan the architecture: Should data preparation processes be taken over by QlikView until the switch to Qlik Sense has been completed? Or should Qlik Sense also connect data sources directly?

3) QlikView AND Qlik Sense

This route is often chosen by companies with a broad implementation of QlikView.


Often the end users are generally happy QlikView users. But maybe you miss certain possibilities here and there.


Make them available to them in Qlik Sense. In particular, use cases in the areas of self-service, geo-analysis, mobile use, etc.

In the case of new requirements, it is important to consider in which tool the requirement is better placed.


Great attention should also be paid to the architecture: Should QlikView and Qlik Sense connect data sources directly? Or should QlikView provide the Qlik Sense instance with data or even finished data models?

The following diagram shows these three and classifies them with regard to licenses:


License models

Different similarities
With Qlik Sense a new license model was introduced and in some cases considerably simplified compared to QlikView.


While in QlikView, depending on the number of users, different server components are required, this is completely omitted in Qlik Sense:


In Qlik Sense, neither the Qlik server needs to be licensed, nor is there a license for the publisher functions.


Yes = to be licensed separately and for a fee
No = no additional license required, included in the Qlik Sense Named User License

Dual-use licenses

If companies decide to use Qlik Sense and QlikView together, the dual use licenses create the possibility of using QlikView and Qlik Sense Combine licenses.


Specifically, a combined license is issued. The dual use licenses for Qlik Sense are based on the type and number of existing QlikView licenses.


Simple calculation example: Assume a company has 50 named users and 200 document user licenses. The following overview describes the relationship for the dual-use licenses.


QlikView *Qlik Sense Dual Use
50 named user CALs50 professional
200 Document User CALs200 analyzer **


* Under maintenance, procurement took place before July 1, 2018.
** Qlik Sense users have access to any number of Qlik Sense apps. No restriction similar to Document User CAL.



From QlikView® to Qlik Sense® - ON-DEMAND-EVENT
Is the switch from QlikView® to Qlik Sense® also worthwhile for you?
Do you use QlikView® and want to classify the application area of ​​Qlik Sense®?

>> Register now and learn more!



Would you like to be specific now?


Arrange a free consultation with us 

Call us on +41 44 405 60 50 | Write to us at [email protected]

Or use our contact form.


We look forward to meet you!