Dataset tables

Datasets hold the components of a distributed project together, providing a way to handle a group of points as a unit. They are used to tie RealTime database (RTDB) records to systems and the privileges configured on those systems.

The doas_dataset Table Edit dialog box, shown below contains the list of available table entries that you have configured for the dataset. The points each dataset uses can come from a several table types, for example analog and status records. They can share common properties, but this is not necessary. Generally, datasets will access a mixture of the following tables: analog, rate, status, remote, connection, modem, application, device, spooler, and jsh.

A dataset is an entity within the RealTime database (RTDB). It binds records into groups, which are then given control privileges. These privileges will apply to all of the records within the group.

When a Distributed AVEVA Enterprise SCADA installation is configured, datasets that are specific to the project are created. Privileges are then assigned to these datasets. Privileges define which AVEVA Enterprise SCADA systems can manage and control given datasets. Finally, records in RTDB tables are associated with these datasets.

In the following figure, two datasets are defined. Each dataset associates a set of records to a set of privileges. These privileges may change dynamically during run-time.

It should be possible to associate a dataset to a diverse set of records. The association between a dataset and the points within the dataset should be maintained within the points; each point should contain information describing the dataset to which it is associated.

Note: Points must be created on a system that has visibility to all datasets. If a point is created on a system that does not have visibility to all datasets (and therefore does not have knowledge of all the occupied slots for a table), it is possible that it will unknowingly create a point in a slot that is occupied on another system. The resulting replication collision could result in data loss.

The dataset is the primary relationship marker for DistribuSys privileges and replication rules. Individual records within a table can be assigned to any dataset, independent of their slot number.