Professional Documents
Culture Documents
FactoryTalk Alarm and Event (CPR9 and later) Log Database Schema (Format)
(/app/answers/detail/a_id/60765#)
FactoryTalk Alarm and Event (CPR9 and later) Log Database Schema (Format)
Support Center (/app/home) Menu
60765 | Date Created: 04/22/2009 | Last Updated: 03/30/2015
Email this page Unknown message slot SUBSCRIBE_TO_UPDATES3
Access Level: TechConnect
Question
What is the database schema for the FactoryTalk Alarm and Events (CPR9 and later) historical log?
Answer
The Information below can be found by using any of the following 4 methods:
1) Click Start > Programs > Rockwell Software > FactoryTalk Tools > FactoryTalk Help. Then in the HELP file, click FactoryTalk Alarm and Events > setup alarm history
logging > setup alarm history logging (again) > About the database views > Database schema.
2) In FactoryTalk View Studio in the application explorer tree, click System > Connections. Then rightclick Databases and select New Database... Then click Help.
Search for 'database schema'.
NOTE: There have been no changes in the database schema since CPR9. The information below applies to the CPR9 release and later.
===================================================================
Database schema
The database schema defines the tables and views for the database. Based on the FactoryTalk alarm and event type (simple, condition, or tracking), new rows are added
to the appropriate database tables. From those database tables, the associated default views of the alarm and event data are updated. See the following table for more
information on each event type and database view.
With this event type The following database view is updated
Simple SimpleEvent
(mk:@MSITStore:D:/Program%20Files/Common%20Files/Rockwell/Help/FactoryTalk
ActivationsEHistorianEN.chm::/SimpleEvent_database_table.htm)
Conditionrelated ConditionEvent
(mk:@MSITStore:D:/Program%20Files/Common%20Files/Rockwell/Help/FactoryTalk
ActivationsEHistorianEN.chm::/ConditionEvent_database_table.htm)
Trackingrelated TrackingEvent
(mk:@MSITStore:D:/Program%20Files/Common%20Files/Rockwell/Help/FactoryTalk
ActivationsEHistorianEN.chm::/TrackingEvent_database_table.htm)
Below is the format of the database view(s) created :
SimpleEvent database view
Tip: This view is not used in FactoryTalk Alarms and Events v2.10.00 (CPR9) and is included now for future use. This view will not be populated with alarm and event data.
This view displays all of the fields and properties common to a simple event.
Tip: Messages will be logged in the language specified on the
Alarm Server Properties dialog box.
1 This field is not used in FactoryTalk Alarms and Events v2.10.00 (CPR9) and is included now for future use. The value will be null.
TrackingEvent database view
This view displays all of the fields specific to a tracking event.
1 This field is not used in FactoryTalk Alarms and Events v2.10.00 (CPR9) and is included now for future use. The value will be null.
ConditionEvent database view
This view displays all of the fields and properties common to a conditionrelated (alarm) event.
https://rockwellautomation.custhelp.com/app/answers/detail/a_id/60765 3/6
8/10/2016 60765 FactoryTalk Alarm and Event (CPR9 and later) Log Database Schema (Format)
Tip: You cannot disable areas in FactoryTalk Alarms and Events v2.10.00 (CPR9).
Tip: You cannot suppress areas in FactoryTalk Alarms and Events v2.10.00 (CPR9)
For more information on the specific bit values, see Change Mask Values
(mk:@MSITStore:D:/Program%20Files/Common%20Files/Rockwell/Help/FactoryTalk
ActivationsEHistorianEN.chm::/Change_Mask_Values.htm). ***
For additional supported values that are not addressed by the OPC DA specification,
see Extended Quality Values
(mk:@MSITStore:D:/Program%20Files/Common%20Files/Rockwell/Help/FactoryTalk
ActivationsEHistorianEN.chm::/Extended_Quality_Values.htm).
For more information on the meaning of the standard OPC quality values, see the
OPC DA specification on the OPC Foundation (https://www.opcfoundation.org/)
website.
As a given alarm instance changes state, this ID value will remain constant. For
example, when an alarm becomes active, it will be assigned an ID value; when the
alarm is acknowledged or returns to normal, that same ID value continues to be
logged. Additionally, the same ID will be used for multiple conditions of a level alarm
(for example, the HI and HIHI alarms will use the same ID value since the level alarm
does not return to normal when going from the HI to HIHI states).
1 This field is not used in FactoryTalk Alarms and Events v2.10.00 (CPR9) and is included now for future use. The value will be null.
2 This field is not used in FactoryTalk Alarms and Events v2.10.00 (CPR9) and is included now for future use. The value will match ConditionName.
AllEvents database view
Combines all of the fields from the following into a single view:
· SimpleEvent (mk:@MSITStore:D:/Program%20Files/Common%20Files/Rockwell/Help/FactoryTalk ActivationsEHistorianEN.chm::/SimpleEvent_database_table.htm)
· TrackingEvent (mk:@MSITStore:D:/Program%20Files/Common%20Files/Rockwell/Help/FactoryTalk
ActivationsEHistorianEN.chm::/TrackingEvent_database_table.htm)
· ConditionEvent (mk:@MSITStore:D:/Program%20Files/Common%20Files/Rockwell/Help/FactoryTalk
ActivationsEHistorianEN.chm::/ConditionEvent_database_table.htm)
Tip: The computer identification fields are different in the TrackingEvent (UserComputerID) and ConditionEvent (ComputerID) database views. When these database
views are combined with the SimpleEvent database view to form the AllEvents database view, the ComputerID field is used to represent both UserComputerID and
ComputerID.
DISCLAIMER
This knowledge base web site is intended to provide general technical information on a particular subject or subjects and is not an exhaustive treatment of such subjects.
Accordingly, the information in this web site is not intended to constitute application, design, software or other professional engineering advice or services. Before making
any decision or taking any action, which might affect your equipment, you should consult a qualified professional advisor.
ROCKWELL AUTOMATION DOES NOT WARRANT THE COMPLETENESS, TIMELINESS OR ACCURACY OF ANY OF THE DATA CONTAINED IN THIS WEB SITE AND
MAY MAKE CHANGES THERETO AT ANY TIME IN ITS SOLE DISCRETION WITHOUT NOTICE. FURTHER, ALL INFORMATION CONVEYED HEREBY IS PROVIDED TO
USERS "AS IS." IN NO EVENT SHALL ROCKWELL BE LIABLE FOR ANY DAMAGES OF ANY KIND INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL,
LOSS PROFIT OR DAMAGE, EVEN IF ROCKWELL AUTOMATION HAVE BEEN ADVISED ON THE POSSIBILITY OF SUCH DAMAGES.
ROCKWELL AUTOMATION DISCLAIMS ALL WARRANTIES WHETHER EXPRESSED OR IMPLIED IN RESPECT OF THE INFORMATION (INCLUDING SOFTWARE)
PROVIDED HEREBY, INCLUDING THE IMPLIED WARRANTIES OF FITNESS FOR A PARTICULAR PURPOSE, MERCHANTABILITY, AND NONINFRINGEMENT. Note
that certain jurisdictions do not countenance the exclusion of implied warranties; thus, this disclaimer may not apply to you.
https://rockwellautomation.custhelp.com/app/answers/detail/a_id/60765 5/6
8/10/2016 60765 FactoryTalk Alarm and Event (CPR9 and later) Log Database Schema (Format)
This page is best viewed in Internet Explorer 10, Firefox 31, Chrome 37, Safari 6 or newer.
(http://www.rockwellautomation.com/global/blog/overview.page)
(https://www.facebook.com/ROKAutomation)
(https://plus.google.com/+RockwellautomationInc)
(https://www.linkedin.com/company/rockwell
(http://www.slideshare.net/RockwellAutomation)
(http://twitter.com/ROKAutomation)
(http://www.youtube.com/rokautomation)
automation)
Top (/app/answers/detail/a_id/60765#top)
https://rockwellautomation.custhelp.com/app/answers/detail/a_id/60765 6/6