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

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

do NOT top-post which makes threads unreadable

Am 21.09.2012 15:55, schrieb Girish Talluru:
> On Fri, Sep 21, 2012 at 6:44 AM, Reindl Harald <h.reindl@stripped =
<mailto:h.reindl@stripped>> wrote:
>     Am 21.09.2012 15:26, schrieb Girish Talluru:
>     > 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?
>=20
>     no because this depends hardly on your data and what the applicatio=
n
>     does - many things may be faster, some like "select count(*) from"
>     are unacceptable slow if they are called often
>=20
>     however, it is the wrong way to ask foreign people such questions
>=20
>     * try the migration on a staging server
>     * test your application under load on the staging server
>=20
>     if no staging server exists you have done something terrible wrong

> I'm sorry if I ask wrong question here?

you did not ask any question because without knowing
what type of queries on what type of data the application
makes no answer is possible

> At this stage we have to migrate to innodb but as a new guy they
> assigned me to get the risks document ready for migration

and that is why i said "try the migration on a staging server"

setup a virtual machine for testing and look with snapshots
how it behaves - any "paper" before is useless

since MyISAM has no foreign keys it should be easy to
change the table types, the other direction would
be more painful




--------------enigCB17444528C0E7800AEB7F5A
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/

iEYEARECAAYFAlBcdZEACgkQhmBjz394AnnXqwCcDJi2V+ZmQDBojc/y9VFXBlkn
CToAn1HJhVfKDszVZ2f8ZSWVJyqB6NiU
=DJk6
-----END PGP SIGNATURE-----

--------------enigCB17444528C0E7800AEB7F5A--