All Units
Introduction
Core Concepts
Data Connectivity
Dashboard Visualization
Clients
Data Historian
Asset Organization
Alarming & Notifications
Helper Modules
Security
Cloud & IoT
Reporting
Automated Transactions
Business Intelligence
Project Management
Fault Detection & Diagnostics
SPC/SQC Analysis
Energy Analysis
Data Exchange
Total: ~35 min
Few applications will expect all of the data to remain in a single repository, so you will commonly need to think about how to exchange this data with other systems. Hyper Historian includes several connectors that allow for interchange of data with third-party applications over multiple protocols.
SQL Query Engine
The Historian stores data in a binary flat file for efficiency and performance, but it is still accessible as a relational database through they SQL Query Engine.
SQL Query Engine in Stored Procedures
The SQL Query Engine includes a robust list of queries that can be used upon the Historian, opening up the options for how to efficiently access your data.
Export to CSV with Historian Reader
The Historian Reader is a simple to use program that allows for direct export of historical data for a given data point and time range. It will export the data to a CSV file.
Export to SQL with Data Exporter
Certain situations, such as sharing data to third-party systems or providing structured data exports, will call for exporting data logged in the Historian out to a SQL table. The Historian Reader module can help.
Import from CSV with MergeWorX
The Data Historian comes equipped with the MergeWorX module, which allows for direct import of data into the Process Data Historian as an alternative to a tag subscription method of data storage. The most common application for MergeWorX is to process and import data from CSV files into the Historian.
Import Edgecross Files with MergeWorX
Edgecross files are efficient CSV datasets which can be merged automatically into the Data Historian. We explain the data format and the configuration of the MergeWorX service.
Archiving
The Data Historian supports data archiving, allowing you to periodically migrate batches of historical data to a separate disk location. This data can still be accessed and used within the primary Historian application.
Use Aliases in Data Exporter
Parameterization through the use of aliases allows for greater flexibility in the configuration of Historian data exporters. It allows for creative re-use of configurations to improve the scalability of your design.
English
Czech
German
French
Italian
Japanese
Polish