Import a large sql dump file to a MySQL database from command line


Post has moved to


About cmanios

This entry was posted in Databases, mysql and tagged , , , , , , , , , , , , . Bookmark the permalink.

33 Responses to Import a large sql dump file to a MySQL database from command line

  1. Marinos says:

    I have read many articles for importing large dbs in mysql…u made my day..THNX!!!

  2. jeff says:

    Thanks for the article – maybe you can help me out. I’ve taken the steps above and I’m getting an error 2006 (MySQL server has gone away) when trying to import a large file. Any ideas why this might be?

  3. Didier says:

    Thank you very much, your post saved my day. I was having errors when importing large files, your instructions worked like a charm.

  4. I have followed your recommendations, but on Set max_allowed_packet and net_buffer_length I got 1 warning in the query and I don’t know what is it. However, the performance is not increased.

  5. nice guid. thanks, but you had forgotten ‘use databansename;’.

  6. Ken Show says:

    This is simply incredible! Many thanks!

  7. kamalsaleh813 says:

    This worked perfectly for me .. Thank you Very Much!

  8. Stefan says:

    Thanks, it helped me a lot.

  9. mimma says:

    Didn’t work with me . “No database selected”

  10. mimma says:

    oops , sorry ma bad
    everything is fine ^_^

  11. ann b says:

    This is so helpful. Reduced my import time from ~1 hour to 4 minutes. Thank you very much.

  12. Azure says:

    Thank for you article. But how long does it take to import 6GB db? I looking for a solution to import very big db, around 150 million record everday to mysql. Time is very important.

    • cmanios says:

      @Azure: In my situation it took about from 45 minutes to 2 hours to import a 6GB file. This file contained tables with 20-30 million rows with many indexes. Although I am not a MySQL expert, I noticed that you can achieve better performance if you tune your memory settings (like tmp_table_size,max_heap_table_size,max_binlog_size) in my.cnf file.

  13. freij. says:

    Hi there, thank you for this article. It was really helpful for me.

  14. Julius says:

    Thanks for putting this together as a script. Does anyone have an idea how I could combine this with dump files that are compressed? I used to import these databases like this:

    gunzip < "dbdump.sql.gz" | mysql -u xyz -p'..' database

    For small dumps, extracting them before is fine, for large ones this seems somewhat problematic as it requires a lot of spare disk space.

  15. mortona42 says:

    imeron? Timer On?

    • cmanios says:

      Hello mortona42! imeron and imeron2 are just two variables to record start and end datetime of import process. See the updated script.

  16. JustME says:

    Dont forget to select the database before you use your dump.

    USE databasenamehere;

  17. nikunj ghelani says:

    ghanu saras che aa post

  18. kudoh says:

    WORKED ! , Thanks DUDE !!

  19. Ann B says:

    The script you provided works great on mysql 5.5. Thank you. However I recently received a newer PC at work and upgraded the local mysql server from 5.5.37 to 5.7.13-0ubuntu0.16.04.2. The import process duration increased from 5 minutes to 25 minutes. The import file is only 110MB. I see in this post ( that 5.7 is slower. I’ve tried changing several performance tuning settings but with no luck.

  20. Lokesh says:

    Not working in Windows 10 64bit. Works perfectly on Windows 7. I am using Wamp Server on both the machines.
    Windows 7 takes 30 min to import the database and Window 10 takes 1.5 hours for the same database.

    • cmanios says:

      Hello Lokesh!

      You might have to check MySql configuration in my.ini as WAMP Server propably comes with a predefined and preconfigured MySQL installation which might not be optimised for high loads. Some times it may help to tweek innodb_buffer_pool_size parameter.

      Best regards,

  21. Kim says:

    I always use like this :-), that work!
    mysql -u[username] -p[password] database_name < file.sql

  22. Varun says:

    Hi, Can we use this above method for INNODB as well? I was trying to disable indexing. Not sure if setting foreign key check to 0 would be any helpful. Could you please help me out? Sorry, i am a novice in database stuff. Thanks

    • cmanios says:

      Hi Varun!

      All these examples have been used in production databases which use InnoDB as storage engine. MyISAM engine does not have foreign key checks , as far as I am concerned.

  23. Crescenzo says:

    but where i put this script? Thanks

    • cmanios says:

      Hello Crescenzo!

      This is a Linux bash shell script. You can execute it wherever you like in a Linux OS, providing that you have MySQL client installed and have the correct credemtials and permissions to a MySQL database.

      Best regards,

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s