Integration with Microsoft SQL server

While AVEVA Historian distinguishes itself in how it uniquely manages time-based data, it relies on SQL Server for certain foundational functionality.

Static Data Management

The SQL Server Runtime database easily manages relatively static data, like configuration data which does not change at a real-time rate. Over the life of a site, tags are added and deleted, descriptions are changed, and engineering ranges are altered. The Runtime database stores this type of information.

Runtime Database Structure

The Runtime database is the SQL Server online database for the entire AVEVA Historian. The Runtime database is shipped with a set of standard database entities, such as tables, views, and stored procedures to store configuration data for a typical factory. You can use the Configuration Editor within the Operations Control Management Console to easily add configuration data to the Runtime database that reflects your factory environment.

OLE DB Interface

Microsoft SQL Server Object Linking and Embedding for Databases (OLE DB) is used to access the time-based data that the Historian stores outside of the SQL Server database. You can query the Microsoft SQL Server for both configuration information in the Runtime database and historical data on disk, and the integration appears seamless.

Historian also leverages SQL Server features such as database security, replication, and backups.