[Imported] Merging of Historical Data

[sbeadle]

>>Message imported from previous forum - Category:ClearSCADA Software<<
User: swanandsathe, originally posted: 2019-08-09 08:55:04 Id:483
Hi,
I am new to this forum, Just keen to understand how to merge historical data of one ClearSCADA server into the other clearSCADA server. We are having two different clearSCADA installations say A and B. We want to decommission server A and wanted to make Server B as central server. Please advise how to merge historical data and configuration of server A into Server B? What precautions should be taken care?

[sbeadle · Accepted solution]

>>Responses imported from previous forum

Reply From User: sbeadle, posted: 2019-08-09 08:59:38
If they are intended to be the same database configuration, can you make B a Standby to A?

Reply From User: swanandsathe, posted: 2019-08-09 11:04:05
No, Server B has its own configuration and we will be appending it with configured objects from Server A like wise we will be merging configured objects from few more servers into Server B. [at]sbeadle said:
If they are intended to be the same database configuration, can you make B a Standby to A?

Reply From User: sbeadle, posted: 2019-08-09 12:00:07
Hi. See this page: https://community.se.com/t5/Geo-SCADA-Knowledge-Base/Resource-Center-Home/ba-p/279133
There is a tool called 'Export and Import History Tool'.
This lets you select points in a source database and export history to CSV files.
And you can use it for import to a destination database.
Note that the filenames are the point names, so if the destination database has different point names you will need to rename the files similarly.

Reply From User: BevanWeiss, posted: 2019-08-12 01:07:52
As noted by Steve, this is generally done by using some form of 'scripting', often within Excel VBA using the Automation Interface (or the .NET API).

The problem with such export/import/migration 'tools' is that they are generally developed as part of a commercial arrangement (by System Integrators) and hence releasing them into the public domain isn't seen as being favourable (since there's not much money to be made from that).
If you look into the Automation Interface / .NET API documentation you will see that raw historic migration isn't too difficult. There are a few Historic.LoadData... methods that you can call and push in data in various formats.
Getting the original data can be done in a few different ways also (Automation Interface / .NET API / SQL etc).

If you need to synchronise Event Journal information, or Property Changes etc etc etc then that starts to get a tiny little bit more tricky.

Reply From User: swanandsathe, posted: 2019-08-12 06:42:46
Thanks for your info, I will check and revert back

Reply From User: rwallace, posted: 2019-08-26 04:01:55
One gotcha about the 'Export and Import History Tool' mentioned by sbeadle is that it does not export the milliseconds part of the data timestamp (at least when I tested it last year)