Tagnames are not logged with the data values, only a numeric tagid.Looking at the contents of the table, we see that the data is not easily understood at first glance:Ī few things stand out here, which will pose a challenge for reporting on the data: We will assume that a single table will be used. If partitioning were enabled, multiple tables (named like sql_data_1_2014_10 below – containing data for the month of Oct, 2014) would be created. With no data partitioning configured, a single table, named sqlth_1_data below, is created, and all data will be logged to that table. The image below shows a database for the Ignition “Demo” project, created in the MySQL database system. Once the historical logging has been configured in Ignition, the project’s database will get created, with the necessary tables. This is preferable for reporting, as you will always have a specific set of tables to work with, but may result in slower historical trend updates in Ignition. To address this, you can configure a very log data partition – say, 10 years – or, simply not check the “Enable Data Partitioning” option. The downside to the data partitioning is that from reporting standpoint, it is difficult to know which table name(s) to query. From a trending (or query) efficiency standpoint, smaller tables of data can be queried, allowing for faster data retrieval. What this means is that every month, a new table will be created in the SQL database, and the tag history will be logged to that month’s table. The default data partition length is set for 1 Month. Then, under the “Tags – History” configuration, you can specify how the data is “partitioned” – i.e., the mechanism by which new tables are created periodically in which the data will be logged: In the Ignition configuration environment, the project database is configured by creating a connection to a specific database, on a specific database platform (MySQL, MS SQL Server, etc.) Dream Report can access either of these data table types, but with slightly different approaches. Another method is to create “Transaction” groups in Ignition Designer, where you select the items/tags to be logged, storage rate, and the specific SQL table into which the data will be logged. One of the methods is to simply select tags to be historized for trending, and they will be logged to a set of “generic” tables in the project’s database. Ignition provides a few different ways to log process data into SQL database. We’ve created the following information to help you configure Ignition for use with Dream Report. Dream Report is a recommended solution for Inductive Automation’s Ignition HMI/SCADA solution. As such, we’ve worked together to test the connectivity and operation of each product.
Inductive Automation is a member of the Dream Report Proven Partner Program.