Overview
Archive Locations offers a flexible way to define and manage where historical data is stored. You can define a default Tag Historian Database and add external options if necessary.
On this page:
| Table of Contents | ||
|---|---|---|
|
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. When configuring the Archive Location, you can use SQL databases, Script Classes, or connections with a Third-Party Historian. In other words, when you set the Archive Location, you specify the storage medium for Tag's 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 Database
You have several options to choose from when defining the default database. In case the default SQLite option does not work for you, you can change it by following the steps below:
- Access Historian → Archive Locations.
- Click on the gear icon 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 next table lists all accepted providers and databases when configuring the default one.
| Provider | Databases |
|---|---|
| SQLite | SQLite |
| Odbc |
|
| OleDb |
|
| OracleClient | Oracle |
| SqlClient |
|
| PostgreeSQL | PostgreeSQL |
Add new Archive Location
If you need additional databases, follow the steps below to add and configure them.
- Access Historian→ Archive Location.
- Click on the plus icon.
- 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.
Archive location Properties
The table below describes the configuration options available when adding a new Archive Location.
Property | Description |
|---|---|
Name | A unique name to identify the new Archive Location. |
Description | Optional description to provide more context or information. |
Store and Forward | 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 Archive Location. Currently, two options are available:
|
Protocol (Only available if using TagProvider) | Defines the protocol used by the External TagProviderTag Provider. Currently, you can use the following options:
|
Station Editor (Only available if using TagProvider) | Configure the connection string to the selected provider and run a test to ensure the setup is correct. |
In this section...
| Page Tree | ||||
|---|---|---|---|---|
|