Historian: At reload an old value is written again / received values with old external timestamp not discarded

• Related Articles

• FAQ: Historian configuration general recommendations

  1. Recommendation on hardware: Storage Memory CPU - SSD (Solid-State Drive). - Disk space capacity as detailed in the attached Excel sheet outputs. - RAM required to load the archive data is about 4 times greater the size of the respective ARX files. ...

• Historian: At redundancy switch old value may be written again in new capsule

  Description In the Historian, when redundancy is triggered, values that are already contained in an archive capsule on server 1 are written again to a new archive capsule on server 2 with the same time stamps. These values should not be written to ...

• FAQ: What is the time zone and time format used in zenon Software Platform products and what needs to be considered?

  When you ask someone what the time is, they'll usually be able to tell you. But when you ask them what date and time sunrise was yesterday in a different country on a different continent, in a different hemisphere it gets less easy. Terms like GMT ...

• Primary Key setting in Metadatabase cannot handle 2 values in the same timestamp for Extended Historian Analysis

  Summary The second fractions were cut away inside the main stored procedures of the reports. The connectors themselves have always supported second fractions. All report templates in these themes now support second fractions: Extended Historian ...

• Archive configuration for best SQL evacuation performance

  The time required to evacuate data to a database increases linearly with the number of insert SQL statements. In earlier zenon versions, recorded values were evacuated to the target database sequentially using single-insert statements. From zenon 11 ...