Discovery and export of very large history databases

Avoid problems when performing History Learn when history database contains extremely large number of records.

Currently the History Auto Learn capability will discover all the Histories in the station, and create a Cloud History Export for each history. This behavior is invoked by clicking the “History Learn” button in the Cloud History Export Manager view. While much faster than performing discovery and individually selecting histories for export, it can lead to problems if the history database contains an extremely large number of records, such as in a station that has several years’ data. The learn process is not yet configurable, and attempting to archive several years’ data, such as will happen on the first archival after the learn, may result in this station, or other systems, being blocked from communicating with Sentience. A future release of NCHSD will provide additional configuration capability so that systems can be integrated into Sentience without problems.

For integrating systems using the NCHSD GA release, please follow these guidelines for history archival:

The best option is to start with a new station, to avoid large history upload.
If you cannot use a new station, we recommend deleting the histories prior to exporting with NCHSD. You can do this from the History Db Maintenance tool. Select all the history devices, then select “Delete All Records” (or “Delete Histories” if using the AX History Db Maintenance view).
If you cannot delete the entire histories, try removing all records before a certain time. If there is a point in time before which the data can be ignored, this may help reduce the size of the database to be exported.

Discovery and export of very large history databases

Related Links