I can`t restore my .sql file to new host.

A

AWC108

New Member
Hi,

I`m trying to restore my .sql file to a new host that I recently bought. It`s a CPanel based and I was trying to do it in MyPHPAdmin but it`s keep saying something like 300 seconds exceeded etc and will load like 73 tables out of 167.

My SQL isn`t very big, only 12MB. Is there any other way to restore this?
 
Create a new MySQL database and user/password.

Import your old one into the new one, if it complains about the time limit re-do it and it'll restart from where it left it. I just had trouble with mine and had to "browse" then select the old one and re-upload it about 9 times. (SQL was 117MB)

Once done, edit the config.php to match the new database info :)
 
Use big dump here the how to:

USAGE

1. Open bigdump.php in a text editor and adjust the database configuration
2. Drop the old tables on the target database if your dump doesn't contain "DROP TABLE" (use phpMyAdmin)
3. Create the working directory (e.g. dump) on your web server
4. If you want to upload the dump files directly from the web browser give the scripts writing permissions on the working directory (e.g. make chmod 777 on a Linux based system). You can upload the dump files from the browser up to the size limit set by the current PHP configuration of the web server. Alternatively you can upload any files via FTP.
5. Upload bigdump.php and the dump files (*.sql or *.gz) via FTP to the working directory (take care of TEXT mode upload for bigdump.php and dump.sql but BINARY mode for dump.gz if uploading from MS Windows).
6. Run the bigdump.php from your browser via URL like http://www.yourdomain.com/dump/bigdump.php. Now you can select the file to be imported from the listing of your working directory.
7. BigDump will start every next import session automatically if you enable the JavaScript in your browser.
8. Relax and wait for the script to finish. Do not close the browser window!
9. IMPORTANT: Remove bigdump.php and your dump files from your server

Note 1: BigDump will fail processing large tables containing extended inserts. An extended insert contains all table entries within one SQL query. BigDump isn't able to split such SQL queries. In most cases BigDump will stop if some query includes to many lines. But if PHP complains that allowed memory size exhausted or MySQL server has gone away your dump probably also contains extended inserts. Please turn off extended inserts when exporting database from phpMyAdmin. If you can run Perl scripts you can try using this script to convert your dump file into a normal dump file without extended inserts.

Note 2: Some web servers disallow script execution in the directory with writing permissions for security reasons. If you changed the permissions on the working directory and you are getting a server error when running the script restore the permissions to their normal state for directories.

Note 3: If Timeout errors still occure you may need to adjust the $linespersession setting in bigdump.php.

Note 4: If mySQL server overrun occures you can use $delaypersession setting to let the script sleep some milliseconds or more before starting next session. This setting will only work if the JavaScript is activated.

Note 5: BigDump is currently not able to restore a single dump file with multiple databases inside (switched by the USE statement).

Note 6: If you experience problems with non-latin characters while using BigDump you have to adjust the $db_connection_char_set configuration variable in bigdump.php to match the encoding of your dump file.

File attached.
More questions : D read the faq:
BigDump: The Staggered MySQL Dump Importer
 
I found SQLDumper to be easier. So I have installed the latest version but when I tried to restore it, I got some error.

2ms2fz7.png
 
You must log in or register to reply here.
Back
Top