I have already made this attempt. And really I stucked into some problems.
I found lots of full text indexes created on the data directory . I don't
know from where they come. We have never created full text indexes for that
database. Slave also was not able to sync with its master. Now, I have
res
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
wrote:
>
> - Original Message -
> > From: "geetanjali mehra"
> > Subject: Changing storage engine in dump file.
> >
> > Is there any implic
Thanks everyone for their reply.
Best Regards,
Geetanjali Mehra
Senior Database Administrator
On Wed, Aug 12, 2015 at 7:07 PM, Reindl Harald
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 a mix
>> of innodb
it is better to take the dump as it is on the master, restore it on the
salve and then change the storage engine through alter table commands that
will be the right way of doing and you could see any issues while
converting from MyISAM to InnoDB.
On Wed, Aug 12, 2015 at 6:51 PM, Johan De Meersman
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
- Original Message -
> From: "geetanjali mehra"
> 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, is that the maximum key lenght for MyI
