SQL Import/Restore

  • bobisimo

    (@bobisimo)


    16 years, 1 month ago

    Hi. I’ve been going through this forum and finding a lot of great information about importing/restoring from an SQL back-up. Unfortunately, I’m not having any luck getting my back-up to properly import, even though my back-up appears (if I view it in a text editor) to have plenty of posts, comments, etc. stashed away.

    I’m wondering if someone has some pointers they can send my way to help me out.

    I’m sure it would be helpful, but I can’t exactly remember how I created my back-up. I thought it might have been with WP-DBManager, but I installed that plug-in and tried an import and, though it reported as successful, nothing imported.

    I also tried MyPHPAdmin and, again, despite success messages, nothing imports. And I’ve tried using the SQL editor through my server provider (1&1), but the largest file they’ll allow is 2 megs and my back-up is about 6.5 megs. Finally, I used the DUMP script that was suggested in one post to get around small size limits and that didn’t seem to do anything either, despite the success report.

    I have a g-zipped version here:
    [Link moderated]

    Hopefully someone can point me in the right direction! 😀

Viewing 3 replies - 1 through 3 (of 3 total)
  • threestyler

    (@threestyler)

    16 years, 1 month ago

    You shouldn’t attach your database as it includes sensitive data, I would suggest you remove it from your post.

    However I was able to install your database on a local server just fine so I would suggest your problem is due to the size of the db, there is probably a tool to split large databases into smaller files or you could manually split the db up just make sure you don’t cut it off mid table. Or you could contact your host who should have the means and be willing to import it for you.

    As you have put your db in the wild I would strongly suggest you change passwords and possibly take some extra security means such as locking down the administration to your ip only.

    Thread Starter bobisimo

    (@bobisimo)

    16 years, 1 month ago

    Well, I appreciate your help and letting me know about the potential problems. I will definitely make some changes to ensure I am protected. 🙂

    I am glad to hear that the database information is valid and not corrupt. I will look around and see what I can find to split the database into smaller chunks. I didn’t even think you could do that manually. That might be the easiest solution.

    I’ll add any updates if I figure something out — in case anyone else has problems and comes across this post.

    Thread Starter bobisimo

    (@bobisimo)

    16 years, 1 month ago

    I used http://www.rusiczki.net/2007/01/24/sql-dump-file-splitter/ to split my database into smaller chunks. That part worked perfectly. Great, easy tool.

    I then tried importing the files using phpMyAdmin as a plug-in on my WordPress blog, or prior to installing WordPress through my server’s tools. Either way, I can import the first 10 or 11 chunks successfully but then it fizzles out and stops giving me feedback. It just hangs and then ends.

    I wrote 1&1 and they said if I upgrade to the next package, they have better tools available for importing. Alas. I think I’m going to just forget about this effort. 🙂

Viewing 3 replies - 1 through 3 (of 3 total)

The topic ‘SQL Import/Restore’ is closed to new replies.