Skip to content
This repository has been archived by the owner on Nov 30, 2022. It is now read-only.

Converting MyISAM tables safely. #171

Open
platform-stephanie opened this issue Oct 5, 2022 · 2 comments
Open

Converting MyISAM tables safely. #171

platform-stephanie opened this issue Oct 5, 2022 · 2 comments

Comments

@platform-stephanie
Copy link

Issue: Topic clarification/correction

Topic Link

https://support.magento.com/hc/en-us/articles/360048389631

Description

MyISAM tables should not be converted to InnoDB with ALTER TABLE on Pro clusters, as they will still lack replication, instead, they should be recreated as InnoDB tables by renaming and copying the data to ensure they will replicate properly:

Rename the existing table.

RENAME TABLE <existing_table> <table_old>;

Create a new table from the data in the existing table.

CREATE TABLE <existing_table> SELECT * from <table_old>;

Additional information

@jmenn
Copy link
Contributor

jmenn commented Oct 7, 2022

Hi there @platform-stephanie!
Thank you for your submission!
We'll take a look!

@barnato-v
Copy link
Collaborator

barnato-v commented Nov 29, 2022

@platform-stephanie Apologies Stephanie. This issue got lost I suspect in preparation for the migration of our content onto Adobe ExL.

I have been assigned to the Jira ticket here https://jira.corp.adobe.com/browse/MSKB-1841

I will creating the PR for this change in our new repo https://git.corp.adobe.com/AdobeDocs/commerce-knowledge-base.en

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

3 participants