Come together with the global Drupal community in Rotterdam, 28 Sept – 1 Oct 2026. Sessions, contribution, connection, and Early Bird savings until 8 June.
By jkestler on
I recently installed a module that seems to have messed with my database tables--my taxonomy terms no longer work, search is messed up, and so on.
I uninstalled the module and still have the same issues.
So, I figure the best solution is to revert to my most recent backup database file (sql).
Is this the best solution, and if so, how should I go about reverting the database? I'm familiar with phpmyadmin, but not the specific commands/process to use.
Thank you for any help!!
Comments
> So, I figure the best
> So, I figure the best solution is to revert to my most recent backup database file (sql)
So you have a back-up gzip file on your desktop? (eg. sql.gz or tar.gz)
Then it's easy:
In phpmyadmin select your database in the left window.
The tables are then listed in the right window.
At the bottom click 'check all', and then to the right, 'with selected' choose 'drop'.
Click ok at the confirm screen.
Your database still exists, but now it has zero tables.
Now go to 'import' - it is a menu tab along the top.
Click 'choose' and navigate to the zip archive on your hard drive.
Your characterset should be utf8, unless you're doing anything weird with the languages on your site.
Leave the other options at '0' and 'none'.
Click 'go'.
time out error
thanks for the guidelines above.
i tried following them, but my phpadmin eventually times out and the tables (and database) don't re-create. i've tried using the gzip and the raw sql db file.
the gzip file is about 3 megs, and the unzipped version is about 18 megs.
any suggestions or alternatives i should try?
thanks again.
> the gzip file is about 3
> the gzip file is about 3 megs
You could try something like bigdump:
http://www.ozerov.de/bigdump.php
http://drupal.org/node/43024
The other thing I'd be tempted to try is a Windows tool like mysqlyog, although
you'd need to be able to connect to your webhost database remotely.
You could also use a WAMP like xampp. Import your database locally, and then export it in three or four parts.
phpmyadmin may be able to import the parts separately into the same database.
As a last ditch attempt, you might ask your webhost whether they'd import it for you.
Been there, too
In general, the raw files work better than the compressed ones.
Time-outs often occur with big databases. Sometimes you can set the relevant php variable higher, but it's more convenient to try bigdump.php, it saved my site more than once.
command line fixed it
thanks everybody. i managed to import the database successfully by:
1. uploading the unzipped sql file it to my public_html folder
2. using the following command line command (with SSH access):
mysql -u USERNAME –p PASSWORD DATABASENAME < MYDATABASE.sql