Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
Hi,
In case we are using Other than QVD files as a source,Qlikview have as in memory capability (or) only we have QVD file need to create for inmemory capability?
Pleas suggest.
Thanks,
Raj.
The main advantage with a QVD file is that you can load it faster than any other data type. In addition, it is a fairly compact format, so that the size of it on disk is reasonably small.
But, just as jontydkpi points out, it does not affect the memory footprint of the app or the size of the qvw/qvf file. It will not reduce its size.
So, there is no need to convert an existing text file to qvd - unless you need to load it fast. And there is no need to create a qvd if you have a good database connection - unless you need to load the table fast.
HIC
I am not quite sure what you are asking, but the source file (QVD or other) makes no difference to the loaded QVW document which will always be in memory.
Your understand is correct, The only correction i am thinking is QVD get reduced some file size and memory which are stored in Inline storage. So, I would suggest you to use always QVD only
QVD will reduce your data upto 10% i believe, so it is best to use.
The main advantage with a QVD file is that you can load it faster than any other data type. In addition, it is a fairly compact format, so that the size of it on disk is reasonably small.
But, just as jontydkpi points out, it does not affect the memory footprint of the app or the size of the qvw/qvf file. It will not reduce its size.
So, there is no need to convert an existing text file to qvd - unless you need to load it fast. And there is no need to create a qvd if you have a good database connection - unless you need to load the table fast.
HIC