Do you want BuboFlash to help you learning these things? Or do you want to add or correct something? Click here to log in or create user.



Question
Why does the Qlikview in-memory (RAM ipv disk) data model not necessarily cause limitations with large amounts of data?
Answer

QlikView utilizes some sophisticated compression algorithms (and some common sense, such as de-duplicating data) to significantly reduce the amount of memory that is required to store data. Typically, on-disk data is compressed to 10 percent of its original size when it is loaded into QlikView.

- It can store / use hundres of millions, even billions of records


Question
Why does the Qlikview in-memory (RAM ipv disk) data model not necessarily cause limitations with large amounts of data?
Answer
?

Question
Why does the Qlikview in-memory (RAM ipv disk) data model not necessarily cause limitations with large amounts of data?
Answer

QlikView utilizes some sophisticated compression algorithms (and some common sense, such as de-duplicating data) to significantly reduce the amount of memory that is required to store data. Typically, on-disk data is compressed to 10 percent of its original size when it is loaded into QlikView.

- It can store / use hundres of millions, even billions of records

If you want to change selection, open document below and click on "Move attachment"

pdf

owner: ngras - (no access) - QlikView 11 for Developers [eBook].pdf, p49

Summary

statusnot learnedmeasured difficulty37% [default]last interval [days]               
repetition number in this series0memorised on               scheduled repetition               
scheduled repetition interval               last repetition or drill

Details

No repetitions


Discussion

Do you want to join discussion? Click here to log in or create user.