Overview
The Historian module implements data storage based on classical table systems. Although an SQLite database is integrated into FrameworkX, the module is also compatible with various other types of databases.
In order to streamline the table creation process across different database types, it is feasible to define generic characteristics. These characteristics will subsequently be employed for table creation in the selected database, designated as ArchiveLocation. This procedure can also be independently conducted directly within the Database Management System (DBMS) in use. The introduction of this abstraction layer enables users to customize settings such as table name, data type, data lifespan, and so forth. This not only facilitates the automatic creation of the table but also provides numerous advantages from the perspective of potential database architectural migrations.
On this page:
| Table of Contents | ||
|---|---|---|
|
Understanding Historian Tables
Historian Tables encompass the organization of tags read from Historian archives, arranging them systematically into Logical tables. These tables play a defining role by specifying the Target Archive database and settings, dictating when and how a specific group of tags is archived.
Definition
:Historian Tables constitute a structured organization of tags from Historian archives, logically arranged into tables with defined settings for archiving within a specified Target Archive database.
Purpose
:Provide user convenience with a configuration interface that encompasses all databases supported by the software.
Function
:Automate the process of creating Historian tables in the database and define how and when groups of tags and properties will have their values recorded.
Operation
:In operation, Historian Tables define the criteria for archiving, including the Target Archive database and specific settings, establishing a comprehensive framework for the storage and retrieval of tagged data.
Application
:Historian Tables find application in the structured organization and storage of tagged data within the Historian system, notably by defining the parameters for archiving in the Target Archive database.
Usage
:To use Historian Tables, users configure settings within the Historian system, specifying the Target Archive database and defining criteria for when and how the associated group of tags should be archived. This feature streamlines data management and retrieval within the Historian system, optimizing efficiency.
Historian Tables Configuration
A historian table delineates some characteristics regarding how data will be written to its target, standardizing requirements for different types of databases. In practice, the software incorporates distinct implementations for various databases, aiming to accomplish identical tasks. However, for the user, the interface remains consistent irrespective of the chosen target.
By default, there is a table automatically created with the project, this table name is "Table1" and your ArchiveLocation is an SQLite.
Properties
| Property | Description |
|---|---|
| Name | Chose a name for the table, the name is chosen by the user, respecting the naming rules. |
| ArchiveLocation | The Target DB's name. For more information, see the Database configuration section. |
| AutoCreate | If true, when run a project with a HistorianTable properly configured, the table will be created automatically into de TargetDB. |
| SaveOnChange | Select to store data in the table (add a row) every time a tag changes that is associated with the table. |
| TimeDeadBand | Enter the minimum logging interval. This is how long the system must wait after storing the value of a tag and before storing a new value. Use with the Save on Change option to avoid creating too many records in the database. |
| LifeTime | Number of days to retain the historian data. After that time, the older rows are automatically deleted from the database. To never delete data, leave this field blank or enter 0 (zero). |
| SaveQuality | Enable or disable the quality of the tag to be stored on the historian table |
| ValueType | |
| Trigger | Use to store data in the table every time a tag or tag property changes. With the Save on Change option, the system stores data in the table when either the tag value changes or the trigger value changes. |
| Normalized | Enable or disable to configure the schema to be used on the historian table |
| Level | |
| Category | |
| LockState | |
| LockOwwner | |
| DateCreated | Date the object was created. |
| DateModified | Date of last editing of the object. |
| Description | Brief description of the historian table |
In this section...
| Page Tree | ||||
|---|---|---|---|---|
|