Archiving Process Data

In addition to using scripts and schedules to write values to the process database, you can use a relational database. Writing values from a relational database is similar to writing values with a script. In both cases, values are written at a pre-defined time or when an event occurs (such as a contact opening). However, unlike scripts and schedules, writing data from a relational database requires that you configure the SQL Trigger and SQL Data blocks in the process database.

These blocks also let you archive data to a relational database. Once the relational database receives and stores the process data, you can query it to retrieve and analyze any information. For more information on setting up and using a relational database, refer to your ODBC manuals and the Using SQL. For more information on process database blocks, refer to the iFIX Database Reference.

IMPORTANT: If you are working in a secure environment and using the Electronic Signature option, you must be aware of the impact of unsigned writes to the process database. Unsigned writes can originate from scripts, schedules, and writes from a relational database. Refer to the Implications of Database Writes With Electronic Signature section of the Using Electronic Signatures manual for detailed information.

 

See Also