Overview
StorageLocations Storage Locations are designated databases that store historical data from Tags on their HistorianTables. It works as the central storage point for this time-series data, enabling long-term trending and analysis essential to industrial processes. System administrators define Storage Locations and configure connection parameters to the chosen database. Historian Tables are then linked to a specific Storage Location, dictating where the table's data will be physically stored.
On this page:
| Table of Contents | ||||
|---|---|---|---|---|
|
Understanding Storage Location
The StorageLocation Storage Location defines where Tag data will be archived establishing a clear linkage between tags and the storage infrastructure. When configuring the StorageLocationStorage Location, you can use:
SQL databases
Script Classes
Connections with a Third-Party Historian
When you set the StorageLocationStorage Location, you specify the storage medium 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 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.
StorageLocation Storage Location Properties
The table below describes the configuration options available when adding a new StorageLocation.
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. |
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 | ||||
|---|---|---|---|---|
|