A2ALMDB database

The A2ALMDB SQL Server database stores alarms and events generated through external sources such as Application Server.

Notes: Starting with AVEVA Historian 2014 R2, alarms and events from Application Server can be stored to history blocks instead of the A2ALMDB database. Also, the Classic Event subsystem stores data in the Runtime database, not the A2ALMDB database. For more information on the Classic Event subsystem, see Configure classic events.

Earlier versions of AVEVA System Platform used WWALMDB database rather than A2ALMDB for alarms and events. If you are currently using WWALMDB and want to to use A2ALMDB instead, you may need to change your alarm historization settings from within the System Platform IDE and change your alarm queries to use A2ALMDB.

Managing the A2ALMDB database is necessary to ensure that the size of the database is maintained within its normal operating parameters. If the database is left unchecked and allowed to grow unbounded, the risk of losing valuable data increases.

You manage the alarm database using two alarm database utilities. Use the Alarm DB Purge-Archive utility to remove records from the database permanently or archive them to files. Use the Alarm DB Restore utility to query previously archived data.

Purging is used to permanently remove data that is no longer required. Archiving allows data to be exported to a file so they can later be restored in needed.

The following figure shows how both utilities purge/archive records and then restore them back to the database.

You must be logged into the computer as an administrator to use the Alarm DB Purge-Archive utility.