How do you suggest to prevent crashed MyISAM table?

On my site was an error:
General Error SQL ERROR [ mysqli ] – Table 'phpbb_sessions' is marked as crashed and should be repaired

I could click to repair that table in mysql manager – PHPMyAdmin and that fixed it. Also the command is: REPAIR TABLE phpbb_sessions;

But the question is how to prevent it. Someone said that MyISAM tables crash like this due to something unexpected, like a server failure, out of memory/disk space or breakdown. There is nothing i can do to prevent it if i am not a…

How do you suggest to prevent crashed MyISAM table?

MySQL 5.6 row format changes when changing storage engine from MyISAM to InnoDB

I am testing an upgrade of all existing MySQL 5.6 tables from MyISAM to InnoDB. I converted all row formats to ‘dynamic’ first for all the tables to be on Barracuda then running “alter table engine = InnoDB” for 16 tables. 12 of the 16 tables changed file formats as well without an alter table command. I am at a loss to understand this. I think this may be related to the .frm files, but I’m not sure how. I’ve checked environment variables:

innodb_file_format is showing Barracuda

innodb_file_format_check is ON

A couple of the tables: Articletranslations is showing as compressed, pubmedabstractauthors and pubmedtranslated are showing as compact. The create table statements from tables that I had changed to dynamic file format before changing the storage engine to InnoDB.

Table: articletranslations

Create Table: CREATE TABLE `articletranslations` (   `TranslationID` int(11) NOT NULL AUTO_INCREMENT,   `ArticleID` int(11) NOT NULL,   `language` varchar(50) COLLATE utf8_unicode_ci DEFAULT NULL,   `TextContent` longtext COLLATE utf8_unicode_ci,   `Name` text COLLATE utf8_unicode_ci,   `Tags` varchar(1000) COLLATE utf8_unicode_ci DEFAULT NULL,   `Detail_Abstract` longtext COLLATE utf8_unicode_ci,   `Disclosures` varchar(2000) COLLATE utf8_unicode_ci DEFAULT NULL,   `Discussion` longtext COLLATE utf8_unicode_ci,   `Acknowledgements` longtext COLLATE utf8_unicode_ci,   `D` longtext COLLATE utf8_unicode_ci,   `Materials` text COLLATE utf8_unicode_ci,   `HTMLTopContent` text COLLATE utf8_unicode_ci,   `Rep_Results` longtext COLLATE utf8_unicode_ci,   `Introduction` text COLLATE utf8_unicode_ci,   `IsMachine` tinyint(1) NOT NULL DEFAULT '1',   `DateTranslated` datetime DEFAULT CURRENT_TIMESTAMP,   PRIMARY KEY (`TranslationID`),   KEY `ArticleTranslations_Language_ArticleID` (`language`,`ArticleID`),   KEY `ArticleTranslations_ArticleID` (`ArticleID`) ) ENGINE=InnoDB AUTO_INCREMENT=177437 DEFAULT CHARSET=utf8 COLLATE=utf8_unicode_ci ROW_FORMAT=COMPRESSED 

Table: pubmedabstractauthors

Create Table: CREATE TABLE `pubmedabstractauthors` (   `AuthorID` int(11) NOT NULL AUTO_INCREMENT,   `ForeName` varchar(255) NOT NULL,   `LastName` varchar(255) NOT NULL,   `Initials` varchar(255) NOT NULL,   PRIMARY KEY (`AuthorID`),   KEY `names` (`ForeName`,`LastName`,`Initials`) ) ENGINE=InnoDB AUTO_INCREMENT=712515 DEFAULT CHARSET=latin1 

Table: pubmedtranslated

Create Table: CREATE TABLE `pubmedtranslated` (   `PMID` int(11) NOT NULL,   `ArticleTitle` text COLLATE utf8_unicode_ci NOT NULL,   `ArticleAbstract` text COLLATE utf8_unicode_ci NOT NULL,   `LanguageID` smallint(6) NOT NULL,   PRIMARY KEY (`PMID`,`LanguageID`) ) ENGINE=InnoDB DEFAULT CHARSET=utf8 COLLATE=utf8_unicode_ci 

Espaço consumido MyISAM vs InnoDB

No MYSQL versão 5.7 o engine InnoDB ainda consome muito mais espaço em disco que o engine MyISAM?

Tenho uma tabela com engine MyISAM com 70 mil inserts por dia e por isso, estou querendo mudar para InnoDB por ter um desempenho superior em escrita, mas sera que o desempenho de escrita no InnoDB vai compensar tanto que o MyISAM? já que com a mudança para InnoDB o aumento de espaço em disco consumido será significativo.

Deleting records and readding in MySQL using MyISAM forgets constraints with Hibernate [migrated]

MySQL – MyISAM – Hibernate

First error in my assumption was that my DB had Foreign Keys. (Not as versed in the different engines provided by MySql)

I was testing a multiple id delete and messed up a line and it deleted everything. I was confused since FK should throw a constraint error.

I had copies of the data so I just imported them back in. Upon running my app the objects are no longer tied to each other.

I am unsure where in the process this gets tied together, I assume Hibernate, but I am not confident where.

Does anyone know where this connection gets defined and how to resolve the issue.