DB Tables Drop on Migration | Azure | MariaDB | MyISAM

  • Resolved Intriguing

    (@intriguingmedia)


    3 years, 10 months ago

    Hi,

    Thanks for an excellent plugin – we use it for all our migrations.

    We’ve migrated this specific package to multiple hosting environments and have had flawless migrations, but run into an issue with a specific hosting provider.

    We have two Gravity form plugins (CRM Perks Salesforce & Gravity Wiz Easy Pass Through) that the database tables are being dropped on migration.

    Got a reply from the hosting team stating “wp ‘all in one’ plugin migrates the sales force plugin on the ‘MyISAM’ engine which is not supported on azure database for MariaDB”.

    If the reply is correct, would it just drop a couple tables only?

    Have you seen this before and are there any possible solutions?

    Thanks

    • This topic was modified 3 years, 10 months ago by Intriguing.
Viewing 1 replies (of 1 total)
  • Plugin Author Yani

    (@yaniiliev)

    The plugin exports the tables with the defined engine – either InnoDB or MyISAM.
    On import, the plugin recreates the tables with the exact engine that they were exported.
    So in your case, the tables were exported with MyISAM and on import, the plugin was not able to create them because of the restriction on Azure MariaDB.

    You will need to change your source website to use InnoDB. Export the database only, then import it and it should work.

    Alternatively:
    1. Create a local WordPress install on your computer
    2. Import the file
    3. Convert all tables to InnoDB
    ALTER TABLE table_name ENGINE=InnoDB;
    More info about converting tables to InnoDB here: https://dev.mysql.com/doc/refman/8.0/en/converting-tables-to-innodb.html
    4. Export the database using the plugin
    5. Import the database onto the new site

Viewing 1 replies (of 1 total)
  • The topic ‘DB Tables Drop on Migration | Azure | MariaDB | MyISAM’ is closed to new replies.