Note: For more information configuring Ignition data logging, please refer to the Ignition product documentation. We will reference this view from Dream Report when creating reports: When we query the v_ignitiondata view, for instance, we see data nicely displayed for reporting. We actually need to create two views вЂ“ one to display the numeric data (integer, float and discrete data points, and one for string tags.) The two views are scripted at follows, but please note that the syntax will vary slightly from one database package to another:ДЇrom_unixtime((`d`.`t_stamp` / 1000)) AS `DateTime`, This table separate table will need to be joined with the sqlth_te table to cross-reference the tag IDвЂ™s with the actual tagnames:ДЇortunately, we can create a SQL вЂњviewвЂќ to organize the data into a human-readable form.

The datestamp is shown in Unix time format.

There are separate fields for integer, float, and string data types.

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.

Inductive automation ignition tags