Girish Talluru <girish.dev1986@xxxxxxxxx> wrote: >Thanks a lot Samuel. Appreciate your help. > >On Fri, Sep 21, 2012 at 6:20 AM, Samuel Lopes Grigolato < >samuel.grigolato@xxxxxxxxx> wrote: > >> Sure, the address you’re looking for is: http://lists.mysql.com/**** >> >> ** ** >> >> Good hunting =)**** >> >> ** ** >> >> *De:* Girish Talluru [mailto:girish.dev1986@xxxxxxxxx] >> *Enviada em:* sexta-feira, 21 de setembro de 2012 10:15 >> *Para:* Samuel Lopes Grigolato >> *Cc:* php-general@xxxxxxxxxxxxx >> *Assunto:* Re: Risks involved in MyISAM to Innodb**** >> >> ** ** >> >> Samuel, Can you please send the DBMS list address?**** >> >> ** ** >> >> Thanks,**** >> >> Girish**** >> >> On Fri, Sep 21, 2012 at 6:08 AM, Samuel Lopes Grigolato < >> samuel.grigolato@xxxxxxxxx> wrote:**** >> >> I would start trying my DBMS user list. Or maybe you're afraid of >impacts >> on >> PHP code? >> >> Cheers. >> >> -----Mensagem original----- >> De: Girish Talluru [mailto:girish.dev1986@xxxxxxxxx] >> Enviada em: sexta-feira, 21 de setembro de 2012 10:04 >> Para: php-general@xxxxxxxxxxxxx >> Assunto: Risks involved in MyISAM to Innodb**** >> >> >> Hi Guys, >> >> I have requirement to change my production database tables which are >using >> myISAM and now bcoz of some changes we have to move to Innodb. >> >> Can anyone suggest how the plan should be and risks involve? >> >> Thanks, >> Girish Talluru >> >> **** >> >> -- >> PHP General Mailing List (http://www.php.net/) >> To unsubscribe, visit: http://www.php.net/unsub.php**** >> >> ** ** >> As it's a Friday... I would back the database up and convert each table one by one. I've not had any data problems ever doing this myself, even on large tables. -- Sent from my Android phone with K-9 Mail. Please excuse my brevity. -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
