We're a Big MyISAM Shop, But...
We have 600 instances of MySQL using MyISAM and it has worked fine for us for more than a decade, so we're not interested in switching to InnoDB. Well, not much anyway. In our opinion, InnoDB is a bloated, fly-infested warthog sweltering in the hot sun, but it does one thing well: row-level locking. After ten years of using MyISAM, we're finally running into some complex queries (very complex!) that are locking up our databases. Sometimes we get tons of "locked" queries stacked up waiting for one complex one to finish.
We don't want to convert the whole database to InnoDB. There are 2000 tables. We suspect that there are only 15-20 tables that really need to be converted. What's the best way to analyze these super complex multi-multi-join queries to determine which tables are actually causing our problems?
Subject
Views
Written By
Posted
We're a Big MyISAM Shop, But...
1574
May 04, 2017 05:46PM
1108
May 04, 2017 06:04PM
1062
May 04, 2017 08:44PM
1141
May 04, 2017 09:46PM
1044
May 05, 2017 11:23AM
Sorry, you can't reply to this topic. It has been closed.
Content reproduced on this site is the property of the respective copyright holders.
It is not reviewed in advance by Oracle and does not necessarily represent the opinion
of Oracle or any other party.