Other Methods of Storing Historical Data
SQL Bridge (Transaction Groups) perform a variety of tasks, one in particular, to store data historically. In their simplest form, transaction groups read values from the OPC addresses, and store them into a SQL database. There are four types of Transaction Groups; Standard, Block, Historical, and Stored Procedures. Each transaction group handles data a little differently.
- Standard Group - is the most flexible, and can also write database values to OPC addresses or synchronize data changes between both the database and PLC. This allows you to create true realtime values tables in a database, and push values to a PLC.
- Historical Group - can quickly store data from the plant floor into any kind of SQL database.
- Block Group - transfers large amounts of data very efficiently.
- Stored Procedures - uses PLC data as inputs and outputs from your existing stored procedures.
Data storage
As mentioned, the historical tag values pass through the store and forward engine before ultimately being stored in the database connection associated with the historian provider. The data is stored according to its datatype directly to a table in the SQL database, with its quality and a millisecond resolution timestamp. The data is only stored on-change, according to the value mode and deadband settings on each tag, thereby avoiding duplicate and unnecessary data storage. The storage of scan class execution statistics ensures the integrity of the data. While advanced users may change the table according to their database to be more efficient (for example, using a compressed engine), Ignition does not perform binary compression or encrypt the data in any way.