Transaction

Forum Moderators: open

Message Too Old, No Replies

Transaction

myISAM to InnoDB

henry0

4:13 pm on Feb 16, 2009 (gmt 0)

In order to take advantage of transaction I am preparing to
ALTER table aaaaa ENGINE=InnoDB
(and do the same to about 15 tables)
Is there a major drawback in changing some tables ENGINE from myISAM to InnoDB knowing that the whole DB will become part ISAM part InnoDB

I believe that there will be a slight loss in speed and space required will also slightly increase but asides the above any other concerns?

coopster

10:43 pm on Mar 13, 2009 (gmt 0)

No replies ... well, after almost a month what did you discover?

henry0

10:24 am on Mar 14, 2009 (gmt 0)

Did lot of researches and found that it was doable
this is part of a large project and it will be implemented within about a month
I will keep you posted
thanks

coopster

11:08 am on Mar 14, 2009 (gmt 0)

Oh yes, it's "doable" ...
[dev.mysql.com...]

I look forward to hearing your thoughts after the conversion. Best wishes!

henry0

11:40 am on Mar 14, 2009 (gmt 0)

I (Since now) am exploring another thought:
No convertion
but rebuild the whole DB as InnoDB, and then insert data back before having thousand of rows to deal with
and we are speaking about 55 tables all together.
My problem is that I really, by all means, need a system similar to transactions
I also explored creating a temp table to load whatever is deleted untill all ops are accomplished
then del the temp if no further needs
but I used temp before, it is not very fast
and is really a one shot deal if something goes wrong with the temp then it's over!

Transaction

myISAM to InnoDB

henry0

coopster

henry0

coopster

henry0

Join The Conversation

Moderators and Top Contributors

Hot Threads This Week