Make sure that all tables in the database use the InnoDB storage engine when you're loading data into your Azure database for MySQL. When you're migrating data from external data sources other than a MySQL database, create flat files and import them by using mysqlimport.īoth Single Server and 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 MySQL 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.Ī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.
![import database workbench import database workbench](https://blogs.sap.com/wp-content/uploads/2018/04/pic4-2.png)
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.
#Import database workbench install#
![import database workbench import database workbench](https://www.joellipman.com/images/screenshots/mysql/mysql_workbench_exportdb_006.png)
Which will show a progress bar as the program runs. Then first install pipe viewer on your OS then try something like this: pv sqlfile.sql | mysql -uxxx -pxxxx dbname If you're just importing from a dump file from the CLI on *nix, e.g. That's why it appears to be hanging while import is progressing in the background.įollowing details were copied from this how-can-i-monitor-the-progress-of-an-import-of-a-large-sql-file accepted answer I assume the actual problem is you don't know the progress percentage of import process.