About the summary action index file
An index file is a file that is automatically created by the summary action.
The index file is index information that identifies which column of which CSV file (or ODBC database table) the actual data is stored in for the definition information of tag fields and calculation fields. This information is used internally by summary actions.By using index files, consistency can be maintained even after operation has started (after historical data or aggregated data has been generated) when fields are added, inserted, or deleted in the tag field master or calculated field master.For example, if a field is deleted from a field master, then any summary actions will store null values for the deleted field's columns (any log data stored before the column was deleted will remain intact).
still,The path of the index file is set in the TagFieldIndex and CalculationFieldIndex properties of the Summary Master File. If you omit these properties, the index file will not be created.Considering the possibility that changes such as adding or deleting columns may be made after operation begins, we recommend setting the system to generate an index file.
|
If you want to initialize all data in the ODBC database, delete the table that stores the data, delete the index file, and then run online again to regenerate the table and index file in the order of the tag field master (this also applies to CSV files). When deleting the index file, be sure to delete the data as a set (note: if you delete only the index file, consistency with the data that was saved up until that point may no longer be maintained). |
|
If you modify the tag field master or calculated field master after starting operation, you will need to take FA-Server offline and then back online in order to apply the modifications.
|