Versions Compared

Old Version 15

changes.mady.by.user Paulo Tsuchiya

Saved on

compared with

New Version Current

changes.mady.by.user Paulo Tsuchiya

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

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 add external options if necessary.

On this page:

Table of Contents
maxLevel3
stylenone

Tip
titleSolution Example

Historian Examples


Understanding

Archive Location

Storage Locations

The Archive Storage 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 Storage Location, you can use:

  • SQL databases

,

  • Script Classes

, or connections

  • Connections with a Third-Party Historians, Like Canary and others. 

When Historian. In other words, when you set the Archive Storage Location, you specify the storage medium system for Tag 's data.

By default, the platform uses an SQLite a SQLite database. You can change the default database or add additional databases if you need to use different ones.

Configuring

The

the 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:

  1. Access Historian →

    Archive

    Storage Locations.

  2. Click on the

    gear icon

    Image Added to open the Dialog.

  3. Define the default database configuration, defining Provider, Database, and Server IP.

  4. Test the database connection. Provide the necessary authentication information and click Test.

  5. Click OK to update the default database.

Image RemovedImage Added

Available Databases

The next table lists all following table provides a list of accepted providers and databases when for configuring the default oneoptions.

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

PostgreeSQL

PostgreSQL

PostgreeSQL

PostgreSQL


Add

new Archive Location

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 locationIf you need additional databases, follow the steps below to add and configure them.

  1. Access

    Historian→ Archive

    Historian → Storage Location.

  2. Click on the

    plus icon

    Image Added.

  3. On the

    Dialog

    dialog, configure the new database. You find the description of each option available in the next section of this documentation page.

  4. Click Ok.

Archive location

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 Archive LocationStorage Location.

Description

Optional description to provide more context or information.

Store and ForwardStoreAndForward

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 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
root@parent
spacesV10