Using the Event Scheduler •Use the  SHOW TRIGGERS  statement. See Section 13.7.7.40, “SHOW TRIGGERS Statement” . The  MySQL Event Scheduler  manages the scheduling and execution of events, that is, tasks that run according to a schedule. The following discussion covers the Event Scheduler and is divided into the following sections: •Section 25.4.1, “Event Scheduler Overview” , provides an introduction to and conceptual overview of MySQL Events. 25.4 Using the Event Scheduler •Section 25.4.3, “Event Syntax” , discusses the SQL statements for creating, altering, and dropping MySQL Events. •Section 25.4.4, “Event Metadata” , shows how to obtain information about events and how this information is stored by the MySQL Server. •Section 25.4.6, “The Event Scheduler and MySQL Privileges” , discusses the privileges required to work with events and the ramifications that events have with regard to privileges when executing. Stored routines require the  events  data dictionary table in the  mysql  system database. This table is created during the MySQL 8.0 installation procedure. If you are upgrading to MySQL 8.0 from an earlier version, be sure to perform the upgrade procedure to make sure that your system database is up to date. See Section 2.11, “Upgrading MySQL” . Additional Resources •You may find the MySQL Event Scheduler User Forum of use when working with scheduled events. •There are some restrictions on the use of events; see Section 25.8, “Restrictions on Stored Programs” . •Binary logging for events takes place as described in Section 25.7, “Stored Program Binary Logging” . 25.4.1 Event Scheduler Overview MySQL Events are tasks that run according to a schedule. Therefore, we sometimes refer to them as scheduled  events. When you create an event, you are creating a named database object containing one or more SQL statements to be executed at one or more regular intervals, beginning and ending at a specific date and time. Conceptually, this is similar to the idea of the Unix  crontab  (also known as a “cron job” ) or the Windows Task Scheduler. Scheduled tasks of this type are also sometimes known as “temporal triggers” , implying that these are objects that are triggered by the passage of time. While this is essentially correct, we prefer to use the term  events  to avoid confusion with triggers of the type discussed in Section 25.3, “Using Triggers” . Events should more specifically not be confused with “temporary triggers” . Whereas a trigger is a database object whose statements are executed in response to a specific type of event that occurs on a given table, a (scheduled) event is an object whose statements are executed in response to the passage of a specified time interval. While there is no provision in the SQL Standard for event scheduling, there are precedents in other database systems, and you may notice some similarities between these implementations and that found in the MySQL Server. MySQL Events have the following major features and properties: 4737