9 - set up historical alarm and event logging, Chapter 9, Set up historical alarm and event logging – Rockwell Automation FactoryTalk Alarms and Events Quick Start User Manual
Page 121
113
Chapter 9
Set up historical alarm and event logging
Use the FactoryTalk Alarm and Event Log Viewer to view alarms and events that have
been logged to a Microsoft SQL Server database that is configured to store historical
alarm and event data
.
Use the Alarm and Event Log Viewer to display entries corresponding to all event
types or to filter the events you want to view. Alarms and events generated during run
time can be logged to a Microsoft SQL Server database.
Simple Events are not supported in this release. A simple event describes a simple
occurrence in the system, such as failure to access a computer or device.
Condition-related events — those that relate to changes in alarm state —and
tracking-related events — those that monitor audited changes to the system — are
supported in this release.
To set up historical alarm and event logging, follow these steps. Each step is explained
in detail in this chapter.
Confirm that the Microsoft SQL Server 2005 Express (SP2) software is installed
(or that you have an existing, compatible version of SQL Server installed – see the
previous Tip).
Add a database definition to your FactoryTalk system.
Associate a database definition with an alarm and event server.
Add an Alarm and Event Log Viewer object to a graphic display.
Run the FactoryTalk View Site Edition Client software and then monitor the
graphic display.
If you do not have a Microsoft SQL Server database installed, we recommend that
you install Microsoft SQL Server 2005 Express (SP2) using the batch file available on
both the FactoryTalk View and RSLinx Enterprise installation CDs in the Redist
folder. For installation instructions, see “Install Microsoft SQL Server 2005 Express”
on page 183.
If you already have Microsoft SQL Server 2000 (SP4) or 2005 installed, you may need
to change the configuration options to log alarm and event messages. For
configuration instructions, see “Use an existing Microsoft SQL Server database” on
page 191.