QVD Optimised Load

[sansimeon]

I have split my facts out into multiple QVD files and they all load as optimized, but the 10 files totalling 2.5gb individually when loaded together save as 8gb, is this correct or should they total 2.5gb still?

[vardhancse]

The way we are joining the multiple fact QVDs will be the impact for the volume increase.

[sansimeon]

Hello  thanks for your reply, I am just concatenating the files into the one table, they do load as optimised as each file has the same fields. Should that impact the size?

thanks

[sujeetsingh]

It depends the way you are using you need to come up with the analysis that the way you are using is best and needed.

Go through this

for more concepts

Best Practices for Data Modelling

[vardhancse]

Yes the way we load will also impact the size.

Like if we concatenate all the records will be loaded.

Left keep/join only related records will be loaded

[ashfaq_haseeb]

Hi,

It depend on lots of factors.

Look at the below post.

http://community.qlik.com/message/473336#473336

Regards

ASHFAQ

[rwunderlich]

Something doesn't smell right about this. QVDs are uncompressed data,

Qlikview Notes: Document Compression

so a QVW that loads a group of QVDs should be smaller (if the QVW is compressed) than the sum of the QVDs or equal (if uncompressed). However, the QVW size also includes the sheet objects. Are there large table charts in the QVW?

I'd suggest using Document Analyzer http://qlikviewcookbook.com/recipes/download-info/document-analyzer/ to review where the memory is distributed in the QVW. You can also load just one QVD into a QVW and use DocAnalyzer to compare the field sizes from that QVW to your total QVW. There is an issue with field sizes getting expanded on QVD loads, but I've only seen that happen in un-optimized loads

-Rob

[sansimeon]

Thank you your document Analyzer was very helpful.