Please ensure Javascript is enabled for purposes of website accessibility
Powered by Zoomin Software. For more details please contactZoomin

AVEVA™ Historian

_AutoReplicationTagEntity

  • Last UpdatedMar 10, 2025
  • 2 minute read

Contains one row for each tag replicated by the system.

Note: This table is for internal use only. Do not edit this table.

Column

Data Type

Description

ReplicationTagEntityKey

int NOT NULL

The unique identifier for the replication tag entity.

(PK) (FK) ReplicationServerKey

int NOT NULL

The unique identifier for the replication server. ReplicationServerKey is a foreign key from the Replication Server table.

(PK) DestinationTagName

TagNameType
(nvarchar(256)) NOT NULL

The name of the destination tag. If the destination tag name is not specified, it is generated based on the naming convention for the replication tag and stored in the database.

DestinationTagID

uniqueidentifier NOT NULL

The unique identifier for the destination tag.

(FK) SourceTagName

TagNameType
(nvarchar(256)) NOT NULL

The name of the source tag. SourceTagName is a foreign key from the Tag table.

(FK) ReplicationGroupKey

int NOT NULL

The unique identification for the replication group. ReplicationGroupKey is a foreign key from the Replication Group table.

MaximumStates

tinyint NOT NULL

Maximum number of states to track for state summary tags. Discrete summary tags have a limit of 3 states. Analog summary tags of a limit of 100 states. The default is 10 states.

(FK) CurrentEditor

tinyint NOT NULL

Used to specify which application or editing environment controls the tag definition. Tags imported from the InTouch HMI software use InTouch as the current editor. If modifications are made to an imported tag in the historian Configuration Editor, then the current editor for the tag is changed to AVEVA Historian. If a re-import is performed, any modifications made using the Configuration Editor are preserved. You can manually maintain InTouch as the current editor for re-importing; however, all changes made to the tag using the Configuration Editor are lost during the re-import. Tags (attributes) that are initially configured using AVEVA Application Server use the ArchestrA Integrated Development Environment (IDE) as the current editor. If you modify an Application Server tag using the historian Configuration Editor, then the current editor for the tag is changed to AVEVA Historian. However, the next time you redeploy the engine, the changes are not preserved. 0 = AVEVA Historian; 1 = InTouch; 2 = AVEVA Application Server.

ReplicationTagEntityId

uniqueidentifier, NOT NULL

This plays a role in SyncQueue to identify the entity.

ChangeVersion

timestamp, NOT NULL

Internal use only.

Status

tinyint NULL

Automatically updated by the system if a change is made to the replication group:
0 = No change; 1 = Insertion;
2 = Modification; 3 = Deletion.

Related Links
TitleResults for “How to create a CRG?”Also Available in