This article clarifies the difference between SQL DELETE and DROP TABLE, showing that DELETE removes rows while preserving table structure (and requires a WHERE clause), whereas DROP TABLE eliminates the entire table, and provides practical scenarios and code examples for each.
This guide explains how to recover accidentally dropped databases, tables, and partitions in StarRocks using the RECOVER command, covering the 1-day default retention window, configuration options, limitations like TRUNCATE and FORCE drops, and practical step-by-step examples with renaming strategies.
This article reviews the long‑standing performance problems of TRUNCATE and DROP TABLE in MySQL, tracing their origins through official manuals and historical bugs, summarizing the optimizations introduced in MySQL 5.5.23, 5.7, 8.0, and 8.4, and offering practical guidance for mitigating remaining latency.
This article investigates why TRUNCATE and DROP TABLE statements appear in MySQL slow‑query logs, analyzes the internal execution paths and performance bottlenecks in MySQL 5.7 and 8.0, and proposes configuration‑based optimizations and debugging techniques to mitigate the latency.
The article analyzes why dropping large InnoDB tables in MySQL can drastically degrade overall database performance due to buffer‑pool mutex and file‑system I/O bottlenecks, and presents both operational work‑arounds and source‑code modifications to alleviate the issue.
This article explains why dropping large MySQL tables can heavily impact server I/O, compares ext3 and ext4 file‑system behavior, and provides a step‑by‑step method using hard links and the truncate tool to minimize downtime and I/O load.
