Learn about rec how to record PI Point database changes for PI Interface for RDBMS

The interface can record changes made to the PI Point Database. The managing tag is triggered by modification of a point attribute. The managing point is configured by setting Location4 to either -1or -2.

Note: AVEVA recommends using the PI System auditing features to audit changes to points, rather than this interface.

Short form configuration - recording current and previous PI point attribute values

When a point with Location4 set to -1 is recognized , the interface expects a subset of the AT.* placeholders in its ExDesc. The INSERT query is executed whenever there was a point attribute change. The keyword /GETPOINTS =pattern (in the ExDesc of the managing point) specifies for which subset of points the changes will be recorded. The pattern syntax follows the one PI SDK's GetPoints () method recohnizes. For example:

/GETPOINTS="pointsource='RDBMS*' AND location1='1'"

or

/GETPOINTS="pointsource='P' OR tag='P2P*'"

By default, the interface checks for attribute changes every two minutes. If an attribute is changed twice within two minutes ending with its original value, the interface will NOT record any change. Since RDBMSPI 3.11, the two-minute interval can be modified by specifying the startup parameter /UPDATEINTERVAL.

Short form example:

INSERT INTO pi_attributes_modified (tagname,
attribute,
changedate,
changer,
newValue,
oldValue)
VALUES (?,?,?,?,?,?);

Configure the target PI point with the following settings:

In the RDBMS, create a table formatted as follows.

Long form configuration

Location4= -2 indicates that all AT.* placeholders can be employed. In this mode, the interface does not remember what the previous attribute value was and forwards only the current PI point attributes state to the corresponding RDB table. The overall principles are the same as with the short form.