Database Allocation

AVEVA Global User Guide

Concepts : Database Allocation

Every database must always exist at the Hub. Constructor databases must also exist at all locations where users need to write to them (the primary location) or read them (secondary locations).

In addition, constructor databases must exist at all locations in the communications network between the Hub and any other location at which they are needed (whether for writing or reading)

The System Administrator at the Hub controls which databases are allocated to each location. If a database is allocated to a location which is not an immediate neighbour of the Hub (that is, not a Child of the Hub), the database will automatically be allocated to all the intermediate locations in the communications network.

System databases at all locations are propagated automatically to all other locations. Transaction databases are automatically allocated and made primary at the locations to which they belong. By default, transaction databases are non-propagating databases. If these databases are required at other locations, they should be allocated there explicitly.