FactoryTalk Alarms and Events Database Update Utility

Use the

FactoryTalk

Alarms and Events Database Update Utility to update the database by:

For earlier versions of

FactoryTalk Alarms and Events

, the response time of

FactoryTalk

Alarm and Event Log Viewer may be very slow. Because it needs to extract historical data from more than one tables (ConditionEvent and TrackingEvent), especially when the tables contain a large volume of data.

Starting from

FactoryTalk Alarms and Events

version 2.90.00 (CPR 9 SR 9), when

FactoryTalk

Alarm and Event Historian logs historical alarm and event data into a database in

Microsoft®

SQL Server®

, an additional table, AllEvent, is created. Starting from

FactoryTalk Alarms and Events

version 6.20.00 (CPR 9 SR 12), ConditionEvent and TrackingEvent tables are no longer created. This data is only logged into the AllEvent table. As a result, by extracting historical data from the AllEvent table, the response time of

FactoryTalk

Alarm and Event Log Viewer is optimized.

By updating the database, the

FactoryTalk Alarms and Events

Database Update Utility merges the ConditionEvent and TrackingEvent tables included in the historical alarm and event database from earlier versions of

FactoryTalk Alarms and Events

into the AllEvent table. All the data in the AllEvent table is queried by

FactoryTalk

Alarm and Event Log Viewer.

If the database is created from earlier versions of

FactoryTalk Alarms and Events

, the AllEvent, Diagnostic, or Messages table may not exist depending on the database schema of that version. Updating the database also creates any of the tables in the database if they don't exist.