Overview

Historical batch information is stored on a AVEVA Batch Management history server. The History server uses Microsoft SQL Server and provides all the historical database requirements for the batch system. At the AVEVA Batch Management Server, a message queue guarantees that data is transmitted to the History server. This guaranteed delivery is accomplished by maintaining the data locally in the case of a disconnection and then retransmitting the data when the connection is restored.

All data is time stamped by the AVEVA Batch Management Server so that if data communications to the History server are interrupted, the time and date stamps are still valid. Data transmission to the History server is managed by the History Queue Manager (HistQMngr), which runs on the AVEVA Batch Management Server.

This documentation does not describe how to use Microsoft SQL Server. However, you may want to use Microsoft SQL Server tools to maintain and view information about the historical databases. For more information on using Microsoft SQL Server, see the Microsoft documentation.

For more information on maintaining your History databases, including history archiving procedures, see "System Administration".

For more information regarding the History server and how to use the reporting system, see Reporting System.

Note:
- AVEVA Batch Management supports Daylight Saving Time (DST) and will accurately log the data into the Batch History database for all the events happening while Spring and Fall DST Time changes. The event records are captured using local time as well as UTC format to represent the right time sequence. AVEVA Batch Management reports data may not be displayed in the order of events for the overlapped period during the DST Fall back.
- AVEVA Batch Management now supports diacritic characters (Czech Republic, Spanish, German, and French). These characters are stored in the AVEVA Batch Management database, and are displayed in the User Interface and Reports. If we update the existing batch entities (such as user name, batch name, and so on) to add diacritic characters, these entities will be stored as new entities in the AVEVA Batch Management database. In addition to the data with existing entities, the Reports will now display the data for the new entities with diacritic characters.