Hello,
Recent experience in both NT6.5 and NT7 has shown me what i consider a big logic contradiction in functionality of NT regarding historical data.
I have the option of saving real time tick data in my PC to be later used as historical data. Drawback (not for me but for some) of this option is that PC has to be on 24/7.
Loading NT before connecting to the data feed shows the data stored on the PC perfectly.
NT servers allow reloading of historical data so that when i connect to my data provider and such data provider doesn't provide historical data NT data servers fill in. The drawback is that it disregards how much data was stored in the PC and completely overwrites the database file.
I think NT should give priority to the amount of data that is stored in the PC before overwriting the db completely.
I know that there is an option for disregarding completely the historical data feed altogether. The drawback is too big IMO, power failures, and other events out of the control of the user would prevent collecting of the data.
If both "store real time data on PC" and "historical data server" functions are available, why can't we have them both playing nice to each other?:
Would it be too difficult to have NT check the time stamp of the last data record in the local database (store real time data on PC function ON) for that particular instrument and use historical data from NT servers fill in ONLY from that point on?
That way if NT historical servers fail, the data missing is not that big of a deal, more if i am a user of the "store real time data on my PC" function.
Thanks
AQ
Recent experience in both NT6.5 and NT7 has shown me what i consider a big logic contradiction in functionality of NT regarding historical data.
I have the option of saving real time tick data in my PC to be later used as historical data. Drawback (not for me but for some) of this option is that PC has to be on 24/7.
Loading NT before connecting to the data feed shows the data stored on the PC perfectly.
NT servers allow reloading of historical data so that when i connect to my data provider and such data provider doesn't provide historical data NT data servers fill in. The drawback is that it disregards how much data was stored in the PC and completely overwrites the database file.
I think NT should give priority to the amount of data that is stored in the PC before overwriting the db completely.
I know that there is an option for disregarding completely the historical data feed altogether. The drawback is too big IMO, power failures, and other events out of the control of the user would prevent collecting of the data.
If both "store real time data on PC" and "historical data server" functions are available, why can't we have them both playing nice to each other?:
Would it be too difficult to have NT check the time stamp of the last data record in the local database (store real time data on PC function ON) for that particular instrument and use historical data from NT servers fill in ONLY from that point on?
That way if NT historical servers fail, the data missing is not that big of a deal, more if i am a user of the "store real time data on my PC" function.
Thanks
AQ
Comment