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 an SQL database defined for Storage Location, Historian Tools and Script Classes that can be added to the solution, as alternate, or concurrent, storage locations.
Understanding Storage Locations
The Storage Location defines where Tag data will be archived establishing a clear linkage between tags and the storage infrastructure. When configuring the Storage Location, you can use:
SQL databases
Script Classes
Connections with Third-Party Historians, Like Canary and others.
When you set the Storage Location, you specify the storage system for Tag data.
By default, the platform uses an 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 Storage Location
Solutions can store data using an external Historian package, or support SQL and multiple Historians concurrently, according to your requirements.
Follow the steps below to add and configure new storage locations.
Access Historian / Storage Locations.
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 Storage Location.
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 with the external database. The data is transferred when the connection is established. |
Storage System | Types available to configure the Storage Location. Currently, two options are available: Tag Provider: Enables you to use external solutions to archive Tag 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 Scripts (Tasks and Classes) documentation. |
Object | The tag provider or script class to use as a storage location. You may also create a new tag provider or script class from this option. |
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. Visit the links above to find out how to configure each tag provider's connection string. |
In this section: