Running a "blind" kill command is often seen as a temporary "band-aid". Without a log, you lose the chance to perform a post-mortem. A script-based approach like killlog.sql provides: December 2013 - CCS Retail Systems
Identifies and stops processes that are consuming excessive CPU, causing massive blocking chains, or hanging indefinitely. killlog.sql
Unlike a standard KILL or ALTER SYSTEM KILL SESSION command, this script records who was killed, what query they were running, and why the action was taken. Why You Need a Logging Script Running a "blind" kill command is often seen
While not a built-in command, is a widely adopted name for a script that automates two critical tasks: causing massive blocking chains