Which database is responsible for maintaining the Historian configuration?

The Runtime database is specifically designed to maintain the configuration settings for the AVEVA Historian. It holds real-time information about how the historian operates, including its parameters and settings, which are crucial for its ongoing performance and management. By utilizing the Runtime database, administrators can ensure that any adjustments or configurations are accurately recorded and can be modified as needed to adapt to operational requirements.

The other databases serve different purposes within the AVEVA Historian ecosystem. The History database is primarily concerned with storing collected historical data, the Archive database is utilized for managing archived data files, and the Event database is focused on logging events and alarms that occur within the system. Each of these plays a pivotal role in data management but does not specifically handle the configuration management like the Runtime database does.