Please ensure Javascript is enabled for purposes of website accessibility
Powered by Zoomin Software. For more details please contactZoomin

AVEVA™ Historian

Runtime database

  • Last UpdatedFeb 27, 2025
  • 1 minute read

The Runtime database is the online database against which the AVEVA Historian runs. The tables within the Runtime database store all configuration information, such as:

  • System configuration

  • Tag definitions

  • InTouch integration information

  • System namespaces and grouping information

  • Classic Event subsystem configuration information

  • User-entered annotations

Runtime database tables are usually used as references or lookup tables by the Historian and client applications. Any changes to the Historian are reflected in these configuration tables. The configuration tables exist as normal SQL Server tables and data within them can be modified by using the Microsoft Transact-SQL query language. For more information on Transact-SQL, see your Microsoft documentation.

The Runtime database also stores some types of history data:

  • Modification tracking data

  • Classic Event subsystem data

Tables that store modification tracking and event data are also normal SQL Server tables.

Finally, the Runtime database is used to logically store historized tag values. Although the tag values are stored in the history block files on disk, the values appear to be saved to tables in the Runtime database. For more information on history blocks, see History blocks and partitions. For more information on retrieving historized tag values, see About data retrieval.

Note: You cannot change the name of the Runtime database.

TitleResults for “How to create a CRG?”Also Available in