Skip to main content
cancel
Showing results for 
Search instead for 
Did you mean: 
Anonymous
Not applicable

Qlikview in memory process?

Questions?

Qlikview does processing In Memory ,How it's work?

1 Solution

Accepted Solutions
andrei_delta
Partner - Creator III
Partner - Creator III

Hello,

"

For the most part, QlikView’s in-memory data structures are quite simple. In particular:

  • QlikView data is stored in a straightforward tabular format.
  • QlikView data is compressed via what QlikTech calls a “symbol table,” but I generally call “dictionary” or “token” compression.
  • QlikView typically gets at its data via scans. There is very little in the way of precomputed aggregates, indexes, and the like. Of course, if the selection happens to be in line with the order in which the records are sorted, you can get great selectivity in a scan.
  • One advantage of doing token compression is that all the fields in a column wind up being the same length. Thus, QlikView holds its data in nice arrays, so the addresses of individual rows can often be easily calculated.

"

and here is the link to article The underlying technology of QlikView | DBMS 2 : DataBase Management System Services

Hope it helps,

Andrei

View solution in original post

3 Replies
Colin-Albert

The Search option can find the answers

Qlikview In-memory technology

alis2063
Creator III
Creator III

when a user clicks on a dashboard, the data is fetched from a noSQL database that can be directly retrieved from RAM without the latency of reading disk, running SQL and other.

Its generally viewed as resulting in industry leading query performance and allows for deep , successive and rapid analytics and exploration of large data sets.

please review the further link

What is in-memory tool?can u explain breifly

andrei_delta
Partner - Creator III
Partner - Creator III

Hello,

"

For the most part, QlikView’s in-memory data structures are quite simple. In particular:

  • QlikView data is stored in a straightforward tabular format.
  • QlikView data is compressed via what QlikTech calls a “symbol table,” but I generally call “dictionary” or “token” compression.
  • QlikView typically gets at its data via scans. There is very little in the way of precomputed aggregates, indexes, and the like. Of course, if the selection happens to be in line with the order in which the records are sorted, you can get great selectivity in a scan.
  • One advantage of doing token compression is that all the fields in a column wind up being the same length. Thus, QlikView holds its data in nice arrays, so the addresses of individual rows can often be easily calculated.

"

and here is the link to article The underlying technology of QlikView | DBMS 2 : DataBase Management System Services

Hope it helps,

Andrei