A cleanup request usually sounds harmless. Remove an old table, tidy the schema, push the change, move on.
In production, that mindset gets people hurt.
When you run drop table in mysql, you are not “clearing data.” You are removing an object the application, reports, jobs, and other tables may still depend on. On a busy hosting stack, that also means touching backup procedures, deployment timing, permissions, and recovery planning. The command is simple. The operational discipline around it is not.
Understanding the Power and Peril of DROP TABLE
DROP TABLE is one of those commands that looks smaller than its blast radius.
MySQL documents that DROP TABLE removes the table definition, all table data, partition definitions and partition data if the table is partitioned, and any triggers associated with that table in one irreversible operation, with lazy eviction improvements arriving in MySQL 8.0.23 (MySQL reference manual).
