Defines how frequently to attempt a failed operation again. This continues until successful execution occurs.

Appears in the Nav tree but not in any manager view and is unique in that it requires no linking of its output for operation.

Getting Started with Niagara documents Retry Trigger properties.

Enables and disables the reporting of the last date and time on a history record.

false queries the database for the last timestamp in the database every time an export descriptor processes data. Depending on the size of the database table and the number of export descriptors being processed, this can be a time consuming activity.

true stores the last timestamp as a property on the export descriptor each time it processes the export. This efficiency-related setting helps with overall system performance when exporting data.

Configures how to normalize the timestamp before writing it to the external database. It includes the time zone.

false normalizes values to the Supervisor station’s time zone.

true writes the original timestamp value (retained by the Supervisor) to the external database. Unfortunately, this option ignores the time zone. This causes difficulties with local time zones, especially in relation to daylight savings time. The Timestamp Storage property exports or updates history timestamps to Coordinated Universal Time (UTC).

Configures histories regarding index creation for new tables. It specifies whether indexes should always be created for new exported history tables.

true ensures that an index on created RDBMS tables for exported histories is always created, no matter what the configuration of other properties is.

false may not create a new index when exporting new tables. The driver may still create indexes based on the configuration of other properties (for example, if Use Last Timestamp is false, indexes get created no matter what).

If this property is false and the Use Last Timestamp property is set to true, an export may not create indexes for the exported tables.

Setting this property to true in that scenario would cause any new tables created going forward to also have a proper index created. You can subsequently use the Migrate To Optimized Table Indexes action against existing exported tables (also those prior to Niagara 4.11) to migrate them and ensure that updated indexes are created in the RDBMS. Creating indexes for exported tables can help maximize query performance.