Use the clause ENGINE=INNODB to set the engine for creating a table, and then transfer the data into the compatible table before the migration. For example, if you have a WordPress or web app that uses the MyISAM engine, first convert the tables by migrating the data into InnoDB tables. If your source database uses another storage engine, convert to the InnoDB engine before you migrate the database. Make sure that all tables in the database use the InnoDB storage engine when you're loading data into your Azure Database for MySQL flexible server instance. When you're migrating data from external data sources other than a MySQL database, create flat files and import them by using mysqlimport.īoth Azure Database for MySQL single server and Azure Database for MySQL flexible server support only the InnoDB storage engine. ![]() Include constraints (primary key, foreign key, and indexes), views, functions, procedures, triggers, and any other database objects that you want to migrate. When you're moving database objects other than tables, explicitly create those objects.For example, use the -include-tables or -exclude-tables switch with mysqlpump, and the -tables switch with mysqldump. By doing so, you can omit any unneeded tables from the migration to save time and resources. When you need to selectively choose a few tables to import from an existing MySQL database into your Azure Database for MySQL flexible server database, it's best to use the import and export technique.For other tools, go to the "Migration Methods" section (page 22) of the MySQL to Azure Database migration guide. ![]() In the following scenarios, use MySQL tools to import and export databases into your MySQL database. In the Azure portal, look for the connection information on the Overview pane of your Azure Database for MySQL flexible server instance.Īdd the connection information to MySQL Workbench.ĭetermine when to use import and export techniquesįor scenarios where you want to dump and restore the entire database, use the dump and restore approach instead. ![]() The database can have the same name as the database that contains the dumped data, or you can create a database with a different name. Download and install MySQL Workbench or another third-party MySQL tool for importing and exporting.Ĭreate a database on the Azure Database for MySQL flexible server instanceĬreate an empty database on the Azure Database for MySQL flexible server instance by using MySQL Workbench, Toad, or Navicat.Create an Azure Database for MySQL flexible server instance by using the Azure portal.Prerequisitesīefore you begin migrating your MySQL database, you need to: This article explains two common approaches to importing and exporting data to an Azure Database for MySQL flexible server instance by using MySQL Workbench.įor detailed and comprehensive migration guidance, see the migration guide resources.įor other migration scenarios, see the Database Migration Guide. For more information about migrating to Azure Database for MySQL flexible server, see What's happening to Azure Database for MySQL Single Server? ![]() We strongly recommend that you upgrade to Azure Database for MySQL flexible server. Azure Database for MySQL single server is on the retirement path.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |