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. Archive Locations offers a flexible way to define and manage where historical data is stored. You can define a default Tag Historian Database and also add external options, if necessary.
Understanding Storage Locations
The Storage
Understanding Archive Location
The Archive Location defines where Tag 's data will be archived considering the Historian Tables arrangement. establishing a clear linkage between tags and the storage infrastructure. You When configuring the Storage Location, you can use:
SQL databases
Script Classes
Connections with a Third-Party Historians, Like Canary and others.
When Historian when configuring the Archive Location. In other words, when you set the Archive Storage Location, you 're specifying specify the storage medium system for Tag 's data.
By default, FrameworX the platform uses an SQLite a SQLite database. You have the option to can change the default database or add additional databases , in case if you need to use different databasesones.
Configuring
Thethe Default SQL Database
You have several options to choose from when defining the default database. In case If you would like to change the default SQLite option does not work for you, you can change it by following database to be something other then the initial SQLite built-in database, follow the steps below:
Access Historian →
ArchiveStorage Locations.
Click on the
gear iconto 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 next following table provides a list all of accepted Providers providers and Databases when databases for configuring the default databaseoptions.
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
new Archive Locationa 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, In case you need additional databases, you can follow the steps below to add and configure them.
Access
Historian→ ArchiveHistorian → Storage Location.
Click on the
plus icon.
On the
Dialogdialog, configure the new database.
The You find the description of each option available
option is described in the next
sessionsection of this documentation page.
Click Ok.
Storage Location Properties
The table below describes the configuration options available when adding a new Archive LocationStorageLocation.
Property | Description |
---|---|
Name | A unique name to identify the new Arquive Storage Location. |
Description | Optional description to provide more context or information. |
Store and ForwardStoreAndForward | If you check this option, FrameworX the platform will store data locally in case of connection failure with the external database. The data is transfer transferred when the connection is restablishedestablished. |
Archive System | The types Types available to configure the Archive locationStorage Location. Currently, two options ar are available: TagProviderTag Provider: Enables you to use external solutions to archive Tag's data. ScriptClassScript Class: For this option, you need to eithercreate a script class or point to existing classes that willto 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 TagProviderTag Provider) | Defines the protocol used by the External TagProviderTag Provider. Currently, you can use the following options: |
Station Editor (Only available if using TagProviderTag Provider) | Configure the connection string to the selected provider and run a test to ensure the setup is correct. |
In this section
...:
Page Tree | ||||
---|---|---|---|---|
|