Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
A QVD is always a QVD, the optimization is important when loading the QVD file.
If you load it optimized, it's a lot faster than loading in an unoptimized way.
The optimization can be broken when doing transformations to the QVD fields.. for example if you use the Replace() function or similar string functions to change the fields when loading from the QVD, this will break the optimization.
Changing names of fields is fine and the QVD will still load optimized.
You can tell if the load is optimized if the load status window shows (QVD) after the load statement.
A QVD is always a QVD, the optimization is important when loading the QVD file.
If you load it optimized, it's a lot faster than loading in an unoptimized way.
The optimization can be broken when doing transformations to the QVD fields.. for example if you use the Replace() function or similar string functions to change the fields when loading from the QVD, this will break the optimization.
Changing names of fields is fine and the QVD will still load optimized.
You can tell if the load is optimized if the load status window shows (QVD) after the load statement.
Hi,
QVD files can be read in two modes, standard (fast) and super-fast. The selected mode is determined automatically by the QlikView script engine. Super-fast mode can be utilized only when all fields or a subset thereof are read without any transformations (formulas acting upon the fields), though the renaming of fields is allowed.
"super-fast mode" is (very approximately) about 10x faster than "standard mode" or about 100x faster than loading the database in the ordinary fashion.
Hope this helps you.
Regards,
Jagan.