# Faulted database - innodb vs myisam

**URL:** <https://forum.inductiveautomation.com/t/faulted-database-innodb-vs-myisam/27847>\
**Category:** Ignition\
**Tags:** ignition80\
**Created:** [August 28, 2019, 5:47pm UTC](https://forum.inductiveautomation.com/t/faulted-database-innodb-vs-myisam/27847 "2019-08-28T17:47:06Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![yehet73190](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/yehet73190/32/68157_2.png) [@yehet73190](https://forum.inductiveautomation.com/u/yehet73190)\
**Post date:** [August 28, 2019, 5:47pm UTC](https://forum.inductiveautomation.com/t/faulted-database-innodb-vs-myisam/27847/1 "2019-08-28T17:47:06Z")

</div>

my database is currently faulted i was able to make the connection valid again using innodb force recovery.

i checked my database and it looks like two of my tables are corrupted, i tried the repair table trick but was not successful i had an error saying

> "The storage engine for the table doesn't support repair mysql"

i did see some solutions that says i can try and switch it over to MyISAM

my concern is if i do that, will it have serious complications on my current database once the tables are repaired? our clients needs the trends and as much as possible we would want to get the data from this table restored because its the month of august, i mean if it was an older month it would probably be okay but since its the current month i might have some issues.

please let me know what your thoughts are. thank you

---

<div class="post-metadata">

**Author:** ![JordanCClark](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/jordancclark/32/83362_2.png) [@JordanCClark](https://forum.inductiveautomation.com/u/JordanCClark)\
**Post date:** [August 29, 2019, 12:21pm UTC](https://forum.inductiveautomation.com/t/faulted-database-innodb-vs-myisam/27847/2 "2019-08-29T12:21:16Z")

</div>

If you are able to start in recovery mode (which it appears you can, judging from the innodb force), I would recommend a dump/drop/reimport as mentioned in this site:

[http://blackbird.si/mysql-corrupted-innodb-tables-recovery-step-by-step-guide/](http://blackbird.si/mysql-corrupted-innodb-tables-recovery-step-by-step-guide/)

---

<div class="post-metadata">

**Author:** ![yehet73190](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/yehet73190/32/68157_2.png) [@yehet73190](https://forum.inductiveautomation.com/u/yehet73190)\
**Post date:** [August 30, 2019, 4:30pm UTC](https://forum.inductiveautomation.com/t/faulted-database-innodb-vs-myisam/27847/3 "2019-08-30T16:30:43Z")

</div>

sorry for the late reply but yes that’s what i ended up doing. thank you