Skip to main content
Announcements
Have questions about Qlik Connect? Join us live on April 10th, at 11 AM ET: SIGN UP NOW
cancel
Showing results for 
Search instead for 
Did you mean: 
Anonymous
Not applicable

QVD size doubling when concatenating 2 identical fact tables

Dear Friends,

I have 2 Fact tables with equal number of columns coming from 2 different subject areas. I have concatenated both tables and storing the concatenated table as QVD. I observed that size of the QVD is almost 3 times of individual QVD sizes of those 2 facts.

Fact1 QVD Size if I store individually: 32 MB( record count 1.3 million)

Fact 2 QVD Size if I store individually: 168 MB ( 9 Million)

After I concatenated 2 tables , Combined QVD size is 486 MB.

Please suggest how I can reduce the size.

Br,

Chinna

21 Replies
Gysbert_Wassenaar

Interesting. Have you checked the record count of the resulting qvd too?


talk is cheap, supply exceeds demand
Anonymous
Not applicable
Author

Hi Gysbert,

No single record increased.

Br,

Chinna

Gysbert_Wassenaar

And the two sources have exactly the same number and same case sensitive names?

And, asking just in case, you're sure you concatenated the tables and did not join them?


talk is cheap, supply exceeds demand
Anonymous
Not applicable
Author

Yeah, exactly Same.

test:

LOAD

  %DayID,

     COMP_CD,

     COMP_CD_DESC_sls,

     %SalesOrgID,

     %CustomerID,

     %ProductHierarchyID,

     %CustomerHierarchyID,

     SLS_FISC_PERIOD,

     #ACT_SALES_AMT_RATE_A,

     #ACT_SALES_AMT_RATE_B,

     #ACT_SALES_AMT_LY_RATE_A,

     #ACT_SALES_AMT_LY_RATE_B,

     #GIT_AMT_OUTBND_RATE_A,

     #GIT_AMT_OUTBND_RATE_B,

     #UNDER_LOGISTICS_AMT_RATE_A,

     #UNDER_LOGISTICS_AMT_RATE_B,

     #UNDER_SALES_AMT_RATE_A,

     #UNDER_SALES_AMT_RATE_B,

     #CRDT_DELIVERY_BLKS_RATE_A,

     #CRDT_DELIVERY_BLKS_RATE_B,

     0 as  #BP_RATE_A,

     0 as #BP_RATE_B,

     0 as #FORECAST_RATE_A,

     0 as #FORECAST_RATE_B

FROM

[$(vQVDPath)SlsJoinWithFact.qvd]

(qvd);

LOAD %DayID,

     COMP_CD,

     COMP_CD_DESC_sls,

     %SalesOrgID,

     %CustomerID,

     %ProductHierarchyID,

     %CustomerHierarchyID,

     SLS_FISC_PERIOD,

     0 as #ACT_SALES_AMT_RATE_A,

     0 as #ACT_SALES_AMT_RATE_B,

     0 as #ACT_SALES_AMT_LY_RATE_A,

     0 as #ACT_SALES_AMT_LY_RATE_B,

     0 as #GIT_AMT_OUTBND_RATE_A,

     0 as #GIT_AMT_OUTBND_RATE_B,

     0 as #UNDER_LOGISTICS_AMT_RATE_A,

     0 as #UNDER_LOGISTICS_AMT_RATE_B,

     0 as #UNDER_SALES_AMT_RATE_A,

     0 as #UNDER_SALES_AMT_RATE_B,

     0 as #CRDT_DELIVERY_BLKS_RATE_A,

     0 as #CRDT_DELIVERY_BLKS_RATE_B,

     #BP_RATE_A,

     #BP_RATE_B,

     #FORECAST_RATE_A,

     #FORECAST_RATE_B

    

FROM

[$(vQVDPath)SlsPlanFact_Final_SPLIT_BP_FC.qvd]

(qvd);

store test into [$(vQVDPath)test.qvd](qvd);

exit script;

Anonymous
Not applicable
Author

Dear Gysbert, Even data types of every items also same. I haven't mentioned concatenate key word . it has automatically concatenated as well. which means both scripts are exactly identical columns .

I'm really clue less .. Pls suggest

Br,

Chinna

Gysbert_Wassenaar

I'm pretty clueless too. If you have a lot of fields with high cardinality I'd expect some size increase because the pointers to the symbol tables will be wider. But a doubling is quite a lot. What happens if you load the big new qvd in a new table and then store it in another qvd?


talk is cheap, supply exceeds demand
ramkrishna86
Creator II
Creator II

Could you please check if load order of all fields are same in both QVD.

Anonymous
Not applicable
Author

Dear Gysbert,still no change in size.

@Ram

load order also same

enriquem
Creator
Creator

And why do you want to reduce de volume?

Kind Regards,
Enrique Mora.