>>Responses imported from previous forum
Reply From User: du5tin, posted: 2019-03-06 17:58:18
CDBHISTORIC is a special table. Because ClearSCADA offers a proper audit log on history the data in CDBHISTORIC is not easily edited via normal database tools. Changes must be made through regular points, script, automation api, etc.
I do know you can bulk load csv files with history for points. Or use the Automation API in a C# app to bulk load values from a database. I have some code for this (moving history from one DB to another).
If you're trying to modify a lot of records on the fly with external DB tools I haven't found a good way to do this. But arguably... is the SCADA host historian the best place to do that modification? Shouldn't that be handled in a system downstream so SCADA can be the operational tool and not the data analytics tool?
What are you trying to accomplish? Maybe that will get the ideas flowing a bit better.
Reply From User: mhd_alm, posted: 2019-03-06 18:24:22
[at]du5tin said:
I do know you can bulk load csv files with history for points. Or use the Automation API in a C# app to bulk load values from a database. I have some code for this (moving history from one DB to another).
This sounds like what I'm trying to achieve here... bulk loading historic values from a DB. I'm dealing with this situation: there's a gap in CDBHISTORIC data due to hardware failure, however there is a parallel data logging system of which data can be used to "repair" ClearSCADA history. Or at least this is what I can think of in order to utilize data logger's data without losing convenience of ClearSCADA trending function.
[at]du5tin said:
If you're trying to modify a lot of records on the fly with external DB tools I haven't found a good way to do this. But arguably... is the SCADA host historian the best place to do that modification? Shouldn't that be handled in a system downstream so SCADA can be the operational tool and not the data analytics tool?
I totally agree with you on this point. SCADA historian better be left with the job it's designed for.
Reply From User: mhd_alm, posted: 2019-03-06 23:02:23
For anyone who's interested, here's the CSV loader [at]du5tin mentioned above:
https://www.schneider-electric.co.th/en/faqs/FA331813/
looks like a suitable option for my need.
Reply From User: adamwoodland, posted: 2019-03-13 01:41:52
Regarding the protected status of CDBHistoric (and friends such as CDBEventJournal), a lot of the larger customer contracts for the projects we deliver have specific requirements regarding the protection of this data to stop users, deliberate or accidentally, deleting key information.
Of course if you have admin access to the servers themselves you can do some serious damage, but that is (or should be!) a very limited set of people.
