Load seperate qvd and reference with qvw

[#1]

I am trying to load realtime data into a qvd as often as possible and then reference that data with a different qvw file that has transactional data.  For example, I have a list of stock trades with volumes and times etc.. that I would like to have in the trade.qvw.  But, I would like to upload itraday pricing into the price.qvd file (incrementally of course) but I do not want to reload the trade.qvw everytime i upload the price.qvd.  Therefore, I want to setup the server to reload the price data into price.qvd and then link to that data with the trade.qvw.

Please share your thoughts.

Thanks

[vgutkovsky · Accepted solution]

Well, if I understood you correctly, you can't actually bring in new QVD data without doing some form of a reload (either full or partial). It sounds like in your case you want to avoid doing a full reload every time pricing changes, maybe because of long reload times? Add something like the following code at the start of your script:

if IsPartialReload() then

DROP TABLE Pricing;

ADD LOAD

...

FROM Pricing.qvd (qvd);

exit script;

End IF

You can then schedule a separate partial reload task with Publisher by checking "Partial Reload" in the task options. This partial reload task can run as often as you want. You can even get really sophisticated with it by checking file modification times and executing only if a new QVD is available, but that's for a separate post

Regards,

Vlad

[#3]

Thanks for the answer Vlad.  Is there a way to test the partial reload in the developer maybe with a button?  Also, do you have to give the partial reload some kind of name so that the publisher or Button knows which partial reload to kickoff?

[vgutkovsky]

You can test Partial Reload either from the File menu or by pressing CTRL+SHIFT+R. A partial reload will execute all commands that are partial-reload-style. These include ADD, REPLACE, DROP, and maybe a few more. You can read about that more in the Help file. You don't want the script to try to execute subsequent DROP statements, for example, so I've put an "exit script" command at the end of the partial reload. You can add other ADD or REPLACE commands inside that same IF. If you want to create multiple partial reload tasks that will each do a different thing, that gets a bit tricky and you would probably have to control that with variables that you pass in through Publisher.

Cheers,
Vlad