Re: what are the functions we can use while creating optimized qvd and unoptimized?
Optimized load is much faster and therefore preferable, especially for larger data sets.
Optimized loads are possible if no transformations (calculations) are made during the load, and no (almost) filtering is done in a WHERE clause.
The only acceptable filter is using function Exists:
So for example this load can't be optimized:
Load * From ... WHERE Country = 'US'
but this load can:
Load * From ... WHERE EXISTS(Country)
On the other hand, the only time you want the load not to be optimized, is if you load a Mapping table from a QVD file. In this case, Optimized load doesn't quite work, so you want to make the load non-optimized deliberately.
Uhh, now I notice the link was created by yourself only. Hope you can understand now that, getting answers from community would not be very helpful for you unless you practice yourself in the real scenario. I have noticed that, you post so many theoritical questions here, seems that you are coming back from interview everytime and posting such questions here. Good, but there is better way; learn qv by practice and just not get answers for interview questions. Otherwise, you will keep memorizing from one end and keep forgetting from other end (something like fixed-lenght-queue). This is what I usually suggest my colleagues who are learning qv.