Unoptimized Load while implementing Section Access

[#1]

While implementing Section Access by loading data from QVD, why do we need to do the load unoptimized?

[Digvijay_Singh]

Check this -

Re: Section Access Script load issue

[marcus_sommer · Accepted solution]

An optimized load transferred the qvd with (nearly) no processing overhead directly into the RAM but some functionalities like section access needs some additionally processing step (in a kind of flagging which fields are used for them and maybe some more) - an optimized load instead will only load field-values and their pointer into the datamodel.

The solution is simple - see the link from above.

- Marcus

[#4]

Thanks Digvijay for the prompt help

[#5]

Thanks Marcus!! for the details.. that was indeed very helpful.

[avinashelite]

just to add a point, the optimized and un optimized load will have difference when your dealing with the huge data set, with a small data set may not see the difference.  If you need the optimized load you can make all the necessary change before storing the data in QVD. Hope this might help you 

[#7]

Thanks Avinash. I had similar query 'If I do all transformation before storing the data in QVD, do I still require to do unoptimized load for section access'.. Thanks once again

[avinashelite]

No need of unoptimized load again, you can directly load the new data from QVD