I have an application with quite some data in it (loaded from QVDs). So reloading of data takes some (too much) time. It seems like quite of a waste of time and processing power that the memory has to be cleared while historic data cannot be changed/deleted in my particular case. Having delta QVD's that update the QVW (without clearing the memory) will keep my data up-to-date while saving loading times.
I'm wondering if any of you have found a solution to this? Is there any difference in how QV desktop and server client handle reloading?
Any other solutions will be appreciated, help or pointers will be appreciated!
I reckon one answer to that would be that it's highly unlikely that anything from the last hour is really relevant in the context of five years of data. Maybe you should not try to do everything in one document.
However if you must have five years of hourly data including the last hour in one document then you're stuck with either reloading everything every hour or some messing about with Dynamic Update actions. See here and here for some information.
I reckon one answer to that would be that it's highly unlikely that anything from the last hour is really relevant in the context of five years of data. Maybe you should not try to do everything in one document.
However if you must have five years of hourly data including the last hour in one document then you're stuck with either reloading everything every hour or some messing about with Dynamic Update actions. See here and here for some information.
