Data Logging in SQL [Part-2] || Factory Talk View Studio || PLC || SCADA

#sql
#datalogging
#factorytalkview
#scada
#plc

Data log is a FactoryTalk View component that collects and stores tag values. Logged data can be stored in an internal file set, or an ODBC-compliant database.
The logged data can be shown in trend or archived for future use. To show historical data in a trend, assign a tag from a data log model to a pen. If you log tag values to an ODBC database, you can view the data in trends, or use third-party, ODBC-compliant tools to analyze and create reports from the
data.

A data log model defines which tags to log data for, when to log the data, and where to log the data.
In the Data Log Models editor, you also specify the format of the log files (file set, or ODBC), and when to create and delete the files (also called records). A single data log model can log data for up to 10,000 tags. At run time, up to 20 data log models can run simultaneously on each FactoryTalk View SE Server.

Use multiple data log models to:
• Store related information in separate file sets.
• Log groups of tags at different rates.
• Log groups of tags based on events.

Logged data can be stored in an internal file set, or an ODBC-compliant database. Each data log file set includes files for storing numeric values (either integers or floating point values), text, and tag names. Internal file sets store tag values in proprietary-format files. You cannot view the contents of the file sets, except in trends.

If you log tag values to an ODBC database, you can view the data in trends, or use third-party, ODBC-compliant tools to analyze and create reports from the data. If the ODBC database becomes unavailable, FactoryTalk View logs the data to backup files in proprietary format.

To use data in multiple formats, define multiple data log models for the same set of tags.