The interesting part about using event triggers is that you can track problems occurring on any
system (local or remote) with greater ease. Although you might want to look at all of those informational
messages in the event log at some point, the SQL Server error message is the one that you
really want to know about the second it occurs. The SQL Server message is an example of an event
log entry that you want to track using an event trigger. Of course, the entry could just as easily
be from any other application. For example, you might want to know when the Windows Time
Service fails to find an online time synchronization source.
448 CHAPTER 18
MONITORING SYSTEM EVENTS AND PERFORMANCE
The EventTriggers utility provides three modes of operation: Create, Delete, and Query. Each one
of these modes controls a particular aspect of working with event triggers. The following sections
discuss these three modes of operation and show how you use them to manage event triggers on
your system.
Create
Before you can use event triggers, you have to create them. The Create mode helps you add new
event triggers. Each event trigger reacts to a separate event in the event log, so you need one event
trigger for each event log entry that you want to monitor.
Pages:
1037
1038
1039
1040
1041
1042
1043
1044
1045
1046
1047
1048
1049
1050
1051
1052
1053
1054
1055
1056
1057
1058
1059
1060
1061