Database interface
- Last UpdatedOct 29, 2026
- 2 minute read
Configuring a database interface with AVEVA Edge is basically linking tasks from AVEVA Edge (Alarms, Events or Trends) to tables of external databases via a specific Database Provider that supports the database you have chosen.
Each history task (Alarm, Events or Trend) can be configured to save data either to files with the proprietary format from AVEVA Edge or to external SQL Relational Databases. Use the Options tab to configure the database to save Alarm and Event history. (See the Trend Folder for instructions for saving history for the trend tasks.)
AVEVA Edge supports ADO.NET to provide an intuitive, simple, flexible and powerful interface with standard technologies from MDAC (Microsoft Data Access Components) such as OLE-DB (Object Linking Embedded — Database) and ODBC (Open Database Connectivity). By using this capability, you can connect to any database that is MDAC compatible (please see the Conformance Table for the list of databases already tested)
The following tasks support the database interface:
-
Alarms: The project can save and/or retrieve the alarm history messages in a relational database.
-
Events: The project can save and/or retrieve the event messages in a relational database.
-
Trends: The project can save and/or retrieve the Trend history values in a relational database.
-
Viewer: Database information can be displayed both in table format (Alarm/Event Control and Grid objects) or in a graphical format (Trend Control object).
-
Web: Because the items listed below are already available in AVEVA Edge Web interface, you can deploy a project that stores/saves data in a relational database and have it working over the Web.
Using its embedded database interface, AVEVA Edge can easily provide data from the plant floor to third-party systems (for example, ERP) or get data from them.
AVEVA Edge can interface with any relational database supported by a valid ADO.NET Provider, OLE DB provider or ODBC driver. However, the conformance tests were executed with the following databases:
|
Database |
Database Version |
ADO.NET Provider |
Assembly Version |
|---|---|---|---|
|
Microsoft SQL Server 2000 |
8.0 |
System.Data.SqlClient |
1.0.5000.0 |
|
Microsoft Access 2000 |
9.0.3821 SR-1 |
System.Data.OleDbClient |
1.0.5000.0 |
|
Microsoft Excel 2000 |
9.0.3821 SR-1 |
System.Data.OleDbClient |
1.0.5000.0 |
|
Oracle |
10g Release 1 for Windows |
System.Data.OracleClient |
1.0.5000.0 |
|
Sybase |
Anywhere 9.0.1.1751 |
iAnywhere.Data.AsaClient |
9.0.1.1751 |
|
MySQL |
4.0.20a |
ByteFX.MySqlClient |
0.7.6.15073 |
For information about how to configure a specific database, please refer to the following: