Qlik is a software company based in Radnor, Pennsylvania, USA (found -1993). Qlik is the provider of QlikView and Qlik Sense, business intelligence& visualization software. QlikView has in-memory intelligence for data loading and analytics which make the result faster than other BI tools.
One of the QlikView’s primary differentiation is the associative user experience it delivers and QlikView is the leading Business Discovery platform.
Associative In-Memory Technology:
QlikView uses an associative in-memory technology to allow users to analyze and process data very fast. Unique entries are only stored in “in-memory (RAM)”everything else is pointers to the parent data. That’s why QlikView is faster and stores more data in memory than traditional cubes. Memory and CPU sizing is very important for QlikView, end user experience is directly connected to the hardware QlikView is running on. The main performance factors are data model complexity, amount of unique data, UI design and concurrent users.
For Example, if you have 2 tables and one is Bank information and another one is for customer information and two tables have a common field (Customer Number). Means that, there is a relationship between two tables and if such a relationship exists, associations are made between the common fields to the tables.
Rules for QlikView Table Association:
1. For two fields association, they should have exact name (case sensitive). Example, “Customer” & “customer” are not considered are same and those fields will not be associated.
2. If some of fields have same exact value from different type of tables, QlikView will consider them as a one value and complete rows will be associated as single row. To associate two fields, those fields should be,
- Same spelling (Case sensitive)
- Same numeric value (008899 & 8899 will get associated)
To know more about basic rules of associative tables please refer the below example.
Customer table column Number and Bank Account table column Number fields are identical and considered as one and same to be associated according to rule 2 (a). Customer table column Name and Address table column Name fields are associated according to rule 2 (b).
Customer Number has the value of 2348 in Customer and Bank Account table, which means John’s Bank Balance, is $893,000.00.
Customer Number has the value of 2348 in Customer table is associated with UK in the field Country in Address table via the name John of the field Name. Alex in Customer table is not same alex in Address table, so there is no association.
An association means links are built between the fields in the tables, so that logical connections can be studied. Same way several tables from one or several databases can be included in the QlikView association.
Components of the QlikView
QlikView Desktop is a windows based desktop tool and that is used by business analytics and developer to create data model and dashboard. Within the environment developer will use a SQL scripting to create connections to the source data to transform data. The file type that is created using the QlikView Desktop is known as a QVW (.qvw, or QlikView file). Upon reload, a QVW can be used to create a data-only QVD (QlikView data) file, which is binary and contains no UI.
QLIKVIEW SERVER (QVS)
QlikView Server (QVS) is a server-side product that contains the in-memory analytics engine and handle / support below processes.
- All client/server communication between a QlikView client and the server.
- QlikView Management Console for administrator access
- Web server (access Point) to provide front-end access to the documents within.
- Client authorization against existing directory providers
- Permit read and write to ACLs (access control lists) for QVW documents.
QLIKVIEW PUBLISHER (QVP)
QlikView Publisher (QVP) is a server based product that performs below functions:
- QVP will help to load the data directly from data source QVW files.
- QVP will be used for distribution service and also refresh the data from QVW source files and distribute to server or PDF reports via email process.
Note: Qlikview can access the below data sources via standard ODBC or OLEB.
- Standard flat files such as Microsoft Excel, XML, etc
- SAP NetWeaver
How QlikView Works:
- When a user first opens a QlikView document, data is loaded in memory – The compressed and un-aggregated data set is loaded off the disk and into the QlikView Server’s RAM (random access memory).
- Users explore data via selections – Central to QlikView is the concept of a user-defined selection state.
- Upon selection, aggregates render instantly – On the fly, QlikView renders aggregates as intuitive and interactive user interface objects: charts, graphs, tables, etc.
- A rich, full, overview of the business – all user interface objects and their underlying aggregates are always in context (associated) with one another. This associative experience gives decision makers a better overview of their business.
- Broad, deep business insights – Nearly all organizations deal with large data sets. Loading large volumes of data into QlikView from a combination of many data sources allows insights into aspects of the organization not otherwise apparent.
- A shared version of the truth for all – QlikView can scale to support thousands of connected users, giving everyone in the organization access to one shared version of the truth.
- Speedy time to value – QlikView is quickly and easily deployed and integrated with existing enterprise systems.
- Low ongoing total cost of ownership – QlikView offers a simple way to create and manage data analysis.
For more details, please click here.
One thought on “Qlik View Architecture – Overview”