Thanks everyone for their reply.
Best Regards,
Geetanjali Mehra
Senior Database Administrator
On Wed, Aug 12, 2015 at 7:07 PM, Reindl Harald h.rei...@thelounge.net
wrote:
Am 12.08.2015 um 15:07 schrieb geetanjali mehra:
I am in the process of creating a new slave. On my master, there is
Depending on the version of MySQL and InnoDB engine, the max key length can
be 3072 for InnoDB..
On Wed, Aug 12, 2015 at 9:21 AM, Johan De Meersman vegiv...@tuxera.be
wrote:
- Original Message -
From: geetanjali mehra mailtogeetanj...@gmail.com
Subject: Changing storage engine
..
On Wed, Aug 12, 2015 at 9:21 AM, Johan De Meersman vegiv...@tuxera.be
wrote:
- Original Message -
From: geetanjali mehra mailtogeetanj...@gmail.com
Subject: Changing storage engine in dump file.
Is there any implications in doing so. Is this approach correct? Will I
face
Hi,
I am in the process of creating a new slave. On my master, there is a mix
of innodb and myisam tables. I want all my tables to be created in innodb
on slave.
I have planned to change the value of storage engine from innodb to myisam
in dump file itself using sed .
Running that dump file on
- Original Message -
From: geetanjali mehra mailtogeetanj...@gmail.com
Subject: Changing storage engine in dump file.
Is there any implications in doing so. Is this approach correct? Will I
face any problem in syncing the slave?
The first thing that occurs to me
vegiv...@tuxera.be
wrote:
- Original Message -
From: geetanjali mehra mailtogeetanj...@gmail.com
Subject: Changing storage engine in dump file.
Is there any implications in doing so. Is this approach correct? Will I
face any problem in syncing the slave?
The first thing
Am 12.08.2015 um 15:07 schrieb geetanjali mehra:
I am in the process of creating a new slave. On my master, there is a mix
of innodb and myisam tables. I want all my tables to be created in innodb
on slave.
I have planned to change the value of storage engine from innodb to myisam
in dump file
