ChatGPT解决这个技术问题 Extra ChatGPT

How do I restore a dump file from mysqldump?

I was given a MySQL database file that I need to restore as a database on my Windows Server 2008 machine.

I tried using MySQL Administrator, but I got the following error:

The selected file was generated by mysqldump and cannot be restored by this application.

How do I get this working?

Great question, thanks for asking this before me, upvoted! Ended up going with a non-accepted solution that worked great, but every method is good. Cheers.

S
Stevi Deter

If the database you want to restore doesn't already exist, you need to create it first.

On the command-line, if you're in the same directory that contains the dumped file, use these commands (with appropriate substitutions):

C:\> mysql -u root -p

mysql> create database mydb;
mysql> use mydb;
mysql> source db_backup.dump;

i personally like this method. it shows progress of the dump and also exactly how much time different sql is taking.
@Phrogz Actually you can supply password on the command line using mysql -u root -psecret without the space, but has the disadvantage that your password shows up in cleartext in process lists and log files. It's better, as you suggest, to use empty -p and type it in the prompt.
This method has the benefit of allowing session-based variables (e.g. FOREIGN_KEY_CHECKS) to be set without having to edit the dump file
this is all well and great when doing this sort of thing by hand, but doesnt work from a bash script.
One drawback: it cannot load gzipped dump (e.g. generated with mysqldump db | gzip -9 > dumpfile.sql.gz)
D
Dave Liepmann

It should be as simple as running this:

mysql -u <user> -p < db_backup.dump

If the dump is of a single database you may have to add a line at the top of the file:

USE <database-name-here>;

If it was a dump of many databases, the use statements are already in there.

To run these commands, open up a command prompt (in Windows) and cd to the directory where the mysql.exe executable is (you may have to look around a bit for it, it'll depend on how you installed mysql, i.e. standalone or as part of a package like WAMP). Once you're in that directory, you should be able to just type the command as I have it above.


Do I use "MySQL Command Line Client"? I've never used MySQL before.
Open up the dump file in a text editor, it's fairly easy to pick through, if there are any "using" statements, then its of multiple databases, if there are none, you'll have to add one at the top before you can run that command.
Of course the database that you put in the "using" statement will have to exist first.
see vogs answer. The syntax is mysql -u<user> -p mydatabasename < db_backup.dump no need for a USE statement at the beginning of the file
"Open up the dump file in a text editor" suggestion seems strange. That might work with small databases or a buffered text editor like EditPad, but with everything else it will choke. It would be nice if you didn't have to take this step.
d
dur

You simply need to run this:

mysql -p -u[user] [database] < db_backup.dump

If the dump contains multiple databases you should omit the database name:

mysql -p -u[user] < db_backup.dump

To run these commands, open up a command prompt (in Windows) and cd to the directory where the mysql.exe executable is (you may have to look around a bit for it, it'll depend on how you installed mysql, i.e. standalone or as part of a package like WAMP). Once you're in that directory, you should be able to just type the command.


w
womd
mysql -u username -p -h localhost DATA-BASE-NAME < data.sql

look here - step 3: this way you dont need the USE statement


p
pdc

When we make a dump file with mysqldump, what it contains is a big SQL script for recreating the databse contents. So we restore it by using starting up MySQL’s command-line client:

mysql -uroot -p 

(where root is our admin user name for MySQL), and once connected to the database we need commands to create the database and read the file in to it:

create database new_db;
use new_db;
\. dumpfile.sql

Details will vary according to which options were used when creating the dump file.


J
Javeed Shakeel

Run the command to enter into the DB

 # mysql -u root -p 

Enter the password for the user Then Create a New DB

mysql> create database MynewDB;
mysql> exit

And make exit.Afetr that.Run this Command

# mysql -u root -p  MynewDB < MynewDB.sql

Then enter into the db and type

mysql> show databases;
mysql> use MynewDB;
mysql> show tables;
mysql> exit

Thats it ........ Your dump will be restored from one DB to another DB

Or else there is an Alternate way for dump restore

# mysql -u root -p 

Then enter into the db and type

mysql> create database MynewDB;
mysql> show databases;
mysql> use MynewDB;
mysql> source MynewDB.sql;
mysql> show tables;
mysql> exit

H
Hengjie

If you want to view the progress of the dump try this:

pv -i 1 -p -t -e /path/to/sql/dump | mysql -u USERNAME -p DATABASE_NAME

You'll of course need 'pv' installed. This command works only on *nix.


Z
Zack Peterson

I got it to work following these steps…

Open MySQL Administrator and connect to server Select "Catalogs" on the left Right click in the lower-left box and choose "Create New Schema" MySQL Administrator http://img204.imageshack.us/img204/7528/adminsx9.th.gif enlarge image Name the new schema (example: "dbn") MySQL New Schema http://img262.imageshack.us/img262/4374/newwa4.th.gif enlarge image Open Windows Command Prompt (cmd) Windows Command Prompt http://img206.imageshack.us/img206/941/startef7.th.gif enlarge image Change directory to MySQL installation folder Execute command: mysql -u root -p dbn < C:\dbn_20080912.dump …where "root" is the name of the user, "dbn" is the database name, and "C:\dbn_20080912.dump" is the path/filename of the mysqldump .dump file MySQL dump restore command line http://img388.imageshack.us/img388/2489/cmdjx0.th.gif enlarge image Enjoy!


M
Michael

As a specific example of a previous answer:

I needed to restore a backup so I could import/migrate it into SQL Server. I installed MySql only, but did not register it as a service or add it to my path as I don't have the need to keep it running.

I used windows explorer to put my dump file in C:\code\dump.sql. Then opened MySql from the start menu item. Created the DB, then ran the source command with the full path like so:

mysql> create database temp
mysql> use temp
mysql> source c:\code\dump.sql

A
Ashwin A

You can try SQLyog 'Execute SQL script' tool to import sql/dump files.

https://i.stack.imgur.com/i2zon.png


J
Jerome_B

Using a 200MB dump file created on Linux to restore on Windows w/ mysql 5.5 , I had more success with the

source file.sql

approach from the mysql prompt than with the

mysql  < file.sql

approach on the command line, that caused some Error 2006 "server has gone away" (on windows)

Weirdly, the service created during (mysql) install refers to a my.ini file that did not exist. I copied the "large" example file to my.ini which I already had modified with the advised increases.

My values are

[mysqld]
max_allowed_packet = 64M
interactive_timeout = 250
wait_timeout = 250

v
vkrishna17
./mysql -u <username> -p <password> -h <host-name like localhost> <database-name> < db_dump-file

This is the same as a couple of the other answers, and this is an eight year old question.
Though the selected answer is very good, this answer was actually more useful for me. My database file was HUGE, and opening it in Notepad++ was a nightmare, it just couldn't handle the size and would not allow me to add the database name at the top of the sql file. In which case being able to specify the db name from the command line is actually more helpful.
The mysql command does not accept spaces between the options and their arguments. It must be -u<username> instead, and the password should not be provided on the command line at all.
佚名

You cannot use the Restore menu in MySQL Admin if the backup / dump wasn't created from there. It's worth a shot though. If you choose to "ignore errors" with the checkbox for that, it will say it completed successfully, although it clearly exits with only a fraction of rows imported...this is with a dump, mind you.


J
Jossef Harush Kadouri

One-liner command to restore the generated SQL from mysqldump

mysql -u <username> -p<password> -e "source <path to sql file>;"

e.g. mysql -u root -p12345678 -e "source /tmp/backup.sql;"
Don't use the password like this just use -p and command line will prompt you a secure password request after you press enter.
When you can afford interactive prompt, you are correct. When you can't (e.g. unattended script) you will probably use it inline
S
Suragch

Assuming you already have the blank database created, you can also restore a database from the command line like this:

mysql databasename < backup.sql

u
user26087

You can also use the restore menu in MySQL Administrator. You just have to open the back-up file, and then click the restore button.


r
rɑːdʒɑ

If you are already inside mysql prompt and assume your dump file dump.sql, then we can also use command as below to restore the dump

mysql> \. dump.sql

If your dump size is larger set max_allowed_packet value to higher. Setting this value will help you to faster restoring of dump.


You should add that before running that command, a user has to select a database to restore the data to with USE DB_NAME
C
CTS_AE

How to Restore MySQL Database with MySQLWorkbench

You can run the drop and create commands in a query tab.

Drop the Schema if it Currently Exists

DROP DATABASE `your_db_name`;

Create a New Schema

CREATE SCHEMA `your_db_name`;

Open Your Dump File

https://i.stack.imgur.com/eUYHJ.png

Click the Open an SQL script in a new query tab icon and choose your db dump file. Then Click Run SQL Script... It will then let you preview the first lines of the SQL dump script. You will then choose the Default Schema Name Next choose the Default Character Set utf8 is normally a safe bet, but you may be able to discern it from looking at the preview lines for something like character_set. Click Run Be patient for large DB restore scripts and watch as your drive space melts away! 🎉