# Killing OPTIMIZE TABLE operation on MyISAM without corrupting data???

**URL:** <https://forums.percona.com/t/killing-optimize-table-operation-on-myisam-without-corrupting-data/566>\
**Category:** Other MySQL® Questions\
**Created:** [December 13, 2007, 2:42pm UTC](https://forums.percona.com/t/killing-optimize-table-operation-on-myisam-without-corrupting-data/566 "2007-12-13T14:42:56Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![vpestovnikov](https://avatars.discourse-cdn.com/v4/letter/v/a6a055/32.png) [@vpestovnikov](https://forums.percona.com/u/vpestovnikov)\
**Post date:** [December 13, 2007, 2:42pm UTC](https://forums.percona.com/t/killing-optimize-table-operation-on-myisam-without-corrupting-data/566/1 "2007-12-13T14:42:56Z")

</div>

Hi all,  
Is there any chance to stop OPTIMIZE TABLE operation without data corrupting?

I found this situation if I kill thread ID of an optimizing operation from the processlist, the data became a corrupted.

And the documentation says the same:

Killing a REPAIR TABLE or OPTIMIZE TABLE operation on a MyISAM table results in a table that is corrupted and unusable. Any reads or writes to such a table fail until you optimize or repair it again (without interruption)