Data loading to the database

The date of the last data loading to the database (see the Moving through the list of alarms section) is refreshed when changes in the database occur.

If there are not any changes in the database within five minutes, the CUT field is forcibly updated and then is updated once a minute. At the same time, there is a gap from the current system time of 5 minutes. After the information from any of the Agents of Control occurs, the CUT becomes equal to the current system time of the computer.

The data loading to the database is performed by the Data loader for Monitoring module.

If files with technical information are received from Agents of Control (for example, a camera is disabled), these files are loaded to the database with a periodicity specified when you configure the Data loader in the Loading period (sec) parameter (10 seconds by default). If files with information on alarms are received from Agents of Control (for example, a vibration sensor generates an event), then this information is loaded to the database immediately.

After each loading to the database, a message is sent to the Control panel interface component to update the information.

If, after receiving files of technical condition, the Server of Control determines that the object state isn't changed, then nothing is loaded to the database. This is why the timer is used to forcibly update interfaces (see the Data loading from database to the interface objects section).

In the Alarm date field in the interface objects, you must specify exactly the time of loading the information on an alarm in the database after receiving it from the Agent of Control, not the time of the alarm appearance at an object.