Overview
Storage Locations are designated databases that store historical data from Tags on their HistorianTables.
Each Storage Location is a repository for time-series data, enabling long-term trending and analysis.
When defining which Tags will store time-series data, those Historian Tags are grouped into Historian Tables, and each Historian Table is located in a Historian Archive Location defined in this interface.
By Default, the system has a SQL database defined for Storage Location, Historian Tools and Script Classes can be added to the solution, as alternate, or concurrent, storage locations. ArchiveLocations provide a flexible mechanism for defining and managing where your historical data will be stored. You can assign a unique name and description to each Target Database, making it easier to identify and manage.
Understanding
ArchiveLocationStorage Locations
The Storage Location defines where Tag data will be archived ArchiveLocation involve the organization of tags within Historian Tables, establishing a clear linkage between tags and the storage infrastructure. The ArchiveLocation can take the form of a SQL database, a ScriptClass, or a connection When configuring the Storage Location, you can use:
SQL databases
Script Classes
Connections with a Third-Party
Definition:
ArchiveLocation encompass the systematic arrangement of tags within Historian Tables, establishing a direct association between tags and the chosen storage medium, which can be a SQL database, a ScriptClass, or a connection with a Third-Party Historian.
Purpose:
The purpose of ArchiveLocation is to provide a structured framework for tags, ensuring their efficient storage and retrieval within Historian Tables, by defining the specific storage medium used.
Function:
ArchiveLocation function as a crucial element in the organization of data, enabling the systematic grouping of tags and the efficient archival of data based on the selected storage medium.
Operation:
In operation, ArchiveLocation specify the storage medium for tags within Historian Tables, allowing for the seamless storage and retrieval of tagged data through a SQL database, a ScriptClass, or a connection with a Third-Party Historian.
Application:
ArchiveLocation find application in the structured organization and storage of tagged data within Historian Tables, particularly by defining the chosen storage medium for optimal data management.
Usage:
To use ArchiveLocation, users configure the storage medium within Historian Tables, choosing between options like a SQL database, ScriptClass, or Third-Party Historian connection. This feature streamlines data management and retrieval within the Historian system, optimizing efficiency.
Historians, Like Canary and others.
When you set the Storage Location, you specify the storage system for Tag data.
By default, the platform uses a SQLite database. You can change the default database or add additional databases if you need to use different ones.
Configuring the Default SQL Database
You have several options to choose from when defining the default database. If you would like to change the default database to be something other then the initial SQLite built-in database, follow the steps below:
Access Historian → Storage Locations.
Click on the
to open the Dialog.
Define the default database configuration, defining Provider, Database, and Server IP.
Test the database connection. Provide the necessary authentication information and click Test.
Click OK to update the default database.
Available Databases
The following table provides a list of accepted providers and databases for configuring the default options.
Provider | Databases |
|---|---|
SQLite | SQLite |
Odbc | Firebird MSAccess2003 MSExcel2003 MySql ODBC_DSN ODBC_FileDsn Oracle SQLServer SQLServer_WA |
OleDb | CSVFile MSAccess2003 MSAccess2007 MSExcel2003 MSExcel2007 Oracle SQLServer SQLServer_WA |
OracleClient | Oracle |
SqlClient | SQLServer SQLServer_WA |
PostgreSQL | PostgreSQL |
Add a new StorageLocation
The solution can store the data using an external Historian package, or support SQL and multiple Historian concurrently, according to your requirements.
Ir other to add other storage location, follow the steps below to add and configure them.
Access Historian → Storage Location.
Click on the
On the dialog, configure the new database. You find the description of each option available in the next section of this documentation page.
Click Ok.
Storage Location Properties
The table below describes the configuration options available when adding a new StorageLocation.
Configuration
On Historian tab, click on ArchiveLocation and the + button.
Fields:
Property | Description |
|---|---|
Name | A unique name to identify the new Storage Location. |
Description |
Optional description to provide more context or information. |
StoreAndForward | If you check this option, the platform will store data locally in case of connection failure |
Target Type:
You have two options to choose from:
ExternalTagSource: In this option, you can select from different ExternalTag Providers such as CanaryLabs, InfluxDB, and GEProficy.
- Station: Here, you configure the connection string to the selected provider and run a test to ensure the setup is correct.
with the external database. The data is transferred when the connection is established. | |
Archive System | Types available to configure the Storage Location. Currently, two options are available: Tag Provider: Enables you to use external solutions to archive Tag's data. Script Class: For this option, you need to |
create a script class or point to existing classes |
to define how the data will be handled and stored. For help creating classes, see the Script, Classes, and Tasks documentation. | |
Protocol (Only available if using Tag Provider) | Defines the protocol used by the External Tag Provider. Currently, you can use the following options: |
Station Editor (Only available if using Tag Provider) | Configure the connection string to the selected provider and run a test to ensure the setup is correct. |
In this section
...:
| Page Tree | ||||
|---|---|---|---|---|
|