Notice in the example above, we did not connect to any server to get this information. That is one of the great things about this utility - you can generate all manner of SQL commands for finding processes and try them out on a test system before incorporating them into your events, triggers, and routines.
We specified the user with the
--match-user option using
a wildcard in case the user is logged in from a different
system. We also specified the name of the maintenance routine in
the same manner in case it gets renamed with a version number or
The output of this utility then is the SQL statement we need to use to find and kill the connections that meet these criteria. Armed with this, we can make a procedure we can call from an event and execute the SQL at a precise time every day.