Replication Tables
- Last UpdatedJul 09, 2023
- 1 minute read
The replication service in a Data Archive collective replicates the key values of critical tables. By replicating the key values, the service ensures that the values are the same on all servers in the collective. With identical key values on all the servers, clients and interfaces can connect to any server to write or access data. For example, because the point tables on the servers share the association for Tag, PointID, and RecNo, interfaces can send identical time-series data to all servers; interfaces need not track different PointID values for each server. Similarly, clients can efficiently retrieve identical time-series data from each server without changing any configuration.
You can only change values of replicated tables at the primary server.
|
PI Table |
Primary, Unique Keys |
Identity Keys |
Foreign Keys |
Replicates to Secondary? |
Can Configure on Secondary? |
|---|---|---|---|---|---|
|
DBSECURITY |
DBName |
UserID, GroupID |
yes |
no |
|
|
PIAFLINK |
no |
no |
|||
|
PIATRSET |
Set |
no |
no |
||
|
PIBAALIAS |
Alias |
no |
yes, but not recommended |
||
|
PIBAUNIT |
UnitName |
UnitID |
PointID, UserID, GroupID |
no |
yes, but not recommended |
|
PICOLLECTIVE |
Name |
yes |
no |
||
|
PIDS |
Set |
SetNo |
yes |
no |
|
|
PIFIREWALL |
Hostmask |
no |
yes |
||
|
PIGROUP |
Group |
GroupID |
yes |
no |
|
|
PIIDENTITY |
Ident |
IdentID |
yes |
no |
|
|
PIIDENTMAP |
IdentMap |
IdentMapID |
PIIdent |
yes |
no |
|
PIMAPPING |
yes |
no |
|||
|
PIMODULES |
UniqueID |
PointID, UserID, GroupID |
yes |
no |
|
|
PIPOINT |
Tag |
PointID, RecNo |
SetNo, UserID, GroupID |
yes |
no |
|
PIPTCLS |
Class |
no |
no |
||
|
PISERVER |
Name |
PICollective.name |
yes |
no |
|
|
PITIMEOUT |
Name |
no |
yes |
||
|
PITRUST |
Trust |
UserID, GroupID |
yes |
no |
|
|
PIUSER |
User |
UserID |
GroupID |
yes |
no |