From: Reindl Harald
Date: September 21 2012 1:44pm
Subject: Re: Risks involved in MyISAM to Innodb
List-Archive: http://lists.mysql.com/mysql/228216
Message-Id: <505C6F27.1080903@thelounge.net>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha1;
 protocol="application/pgp-signature";
 boundary="------------enigA461EF14ABBECDFEA569D342"

--------------enigA461EF14ABBECDFEA569D342
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable



Am 21.09.2012 15:26, schrieb Girish Talluru:
> I have requirement to change my production database tables which are us=
ing
> myISAM and now bcoz of some changes we have to move to Innodb.
>=20
> Can anyone suggest how the plan should be and risks involve?

no because this depends hardly on your data and what the application
does - many things may be faster, some like "select count(*) from"
are unacceptable slow if they are called often

however, it is the wrong way to ask foreign people such questions

* try the migration on a staging server
* test your application under load on the staging server

if no staging server exists you have done something terrible wrong






--------------enigA461EF14ABBECDFEA569D342
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://www.enigmail.net/

iEYEARECAAYFAlBcbycACgkQhmBjz394AnmstgCeNAmG5VE3jIDMM+INabQrz+wR
e9AAn1iy5f1hoxJsTh574gDk3tE8u6sx
=UfB5
-----END PGP SIGNATURE-----

--------------enigA461EF14ABBECDFEA569D342--