Index | Prev | Next

Rdb Archive History Provider

The Rdb Archive History Provider feature was added starting in Niagara 4.11. It allows queries against local history records to be supplemented by archived history records that have been previously exported to a remote RDBMS using the standard RDBMS drivers (rdbSqlServer, rdbMySQL, and rdbOracle). Because it plugs in at a low level in the framework architecture (for example, the history module), existing views that query histories can benefit from this functionality without any additional changes.

This feature can allow you to seamlessly compare baseline years of historical trends with new data using a WebChart.

The standard RDBMS drivers (rdbSqlServer, rdbMySQL, and rdbOracle) can export local history records periodically to a remote database. The Rdb Archive History Provider plugs in to the station’s HistoryService, making it possible for any existing views that query histories to benefit from both local and archived records.

While the station still stores local histories, once the driver exports those history records to a relational database, you can reduce the capacity of those local histories to free up resources in your Supervisor station. At history query time, the Rdb Archive History Provider can easily retrieve those exported (older) archived history records residing in an Oracle, SQL server or MySQL database.

License update prerequisite

To use the Rdb Archive History Provider, your license needs two updates:

  • A general historyArchive license feature that covers any archive history provider implementation
  • A specific rdbHistoryArchive license feature that covers your chosen RDB using the Rdb Archive History Provider against any supported RDBMS.

Related Links

  • Chart example, local data
  • Setting up an Rdb Archive History Provider
  • PX example, local and archive data
  • Common history tasks (Parent Topic)

    • Index | Prev | Next