Show TOC

ALTER EVENT StatementLocate this document in the navigation structure

Changes the definition of an event or its associated handler for automating predefined actions. Also alters the definition of scheduled actions.

Syntax
ALTER EVENT <event-name>DELETE TYPE | TYPE event-type ]
   { WHEREtrigger-condition | NULL }
   | { ADD | [ MODIFY ] | DELETE } SCHEDULE schedule-spec}
   [ ENABLE | DISABLE ]
   [ [ MODIFY ] HANDLER <compound-statement> | DELETE HANDLER}

event-type - (back to Syntax)
   BackupEnd“Connect”  
     |  ConnectFailed 
     |  DatabaseStart 
     |  DBDiskSpace 
     |  “Disconnect” 
     |  GlobalAutoincrement 
     |  GrowDB 
     |  GrowLog 
     |  GrowTemp   
     |  IQMainDBSpaceFree 
     |  IQTempDBSpaceFree 
     |  LogDiskSpace 
     |  “RAISERROR” 
     |  ServerIdle 
     |  TempDiskSpace

trigger-condition - (back to Syntax)
   event_condition<condition-name> ) 
     { = 
       | < 
       | >!= 
       | <= 
       | >= }  <value>

schedule-spec - (back to Syntax)
<schedule-name> ] 
     { START TIME <start-time> | BETWEEN <start-time> AND <end-time> } 
     [ EVERY <period>HOURS  |  MINUTES  | SECONDS } ] 
     [ ON { ( <day-of-week>, … ) | ( <day-of-month>, … ) } ] 
     [ START DATE <start-date> ]
Parameters

(back to top)

  • DELETE TYPE removes an association of the event with an event type.
  • ADD | MODIFY | DELETE SCHEDULE changes the definition of a schedule. Only one schedule can be altered in any one ALTER EVENT statement.
  • WHERE determines the condition under which an event is fired. The WHERE NULL option deletes a condition.
Note For other parameter descriptions, see the CREATE EVENT Statement.
Examples

(back to top)

  • Example 1 lists event names by querying the system table SYSEVENT:
    SELECT event_id, event_name FROM SYS.SYSEVENT
  • Example 2 lists schedule names by querying the system table SYSSCHEDULE:
    SELECT event_id, sched_name FROM SYS.SYSSCHEDULE
Usage

(back to top)

ALTER EVENT lets you alter an event definition created with CREATE EVENT. Possible uses include:
  • Change an event handler during development.
  • Define and test an event handler without a trigger condition or schedule during a development phase, and then add the conditions for execution using ALTER EVENT once the event handler is completed.
  • Disable an event handler temporarily by disabling the event.

When you alter an event using ALTER EVENT, specify the event name and, optionally, the schedule name.

Each event has a unique event ID. Use the event_id columns of SYSEVENT and SYSSCHEDULE to match the event to the associated schedule.

Side effects:
  • Automatic commit
Permissions

(back to top)

Requires one of:
  • MANAGE ANY EVENT system privilege.
  • ALTER ANY OBJECT system privilege.