innoDB vs ISAM

Classic Servoy
1

Our DB is getting very large (total of 300G before Blobs).

We still use ISAM tables in mysql, but am increasingly hearing noises that we should move to InnoDB.

I dont think we have any fulltext tables.

Am I correct in thinking that even though we have not specifically coded for transactions in servoy, that the fact we have autosave swithced on (it is by default i think) and also use plenty of Database Saves, that simply switching a table to InnoDB everything should work seamlessly in servoy, unless there are any specific fields like dates which are being set badly (i.e 0000-00-00) which i understand will cause errors.

Is there anything else major that we need to consider, or is it just a question of testing the code with a new Dev DB where we change the engine to InnoDB?

Is this the right move and is there anything else or other pitfalls we should look out for?

David

2

InnoDB provides support for full transactional tables. MyISAM doesn’t. However, MyISAM is faster.
You can switch without any need to change anything if you aren’t using Database transactions (not servoy auto save).

In general, when I build MySQL databases, I use InnoDB for standard tables, and MyISAM for metadata / lookup tables. This provides transaction support where you need it, and speed for your metadat/lookup tables.