WordPress.org

Ready to get started?Download WordPress

Forums

Move WP to new server (11 posts)

  1. kbeatt
    Member
    Posted 3 years ago #

    My company will be buying a new WordPress server this summer and I want to move our current WP instance to it when it arrives. The only thing is I don't want the current database structure to go with it. Basically, we have been running WPMU since 1.2.1 and I know there are tons of unused database tables and entries that I would not want migrated to the new instance of WP. The only way I can think to do this is to export each site(about 400) and then import them into their new site.

    I really don't want to have to do that for 400 sites. Can someone tell me there is a way to do this without having to export/import 400 times?

    Thanks.

  2. Nope. You either bring the DB with you or ... you don't. And if you don't, it's export/import :/ Which, as you know, does not bring over widgets, themes, etc.

  3. dgilmour
    Member
    Posted 3 years ago #

    There is. If you know the names of the tables you want to lose, then you could:
    - (make sure you've a good backup)
    - take a MySQL dump, complete with drop commands
    - do some nifty text editing to create a file containing the MySQL instructions to drop the unwanted tables
    - use that to drop them all at once

  4. The problem is knowing WHAT tables to drop, though, dgilmour.

  5. dgilmour
    Member
    Posted 3 years ago #

    @Ipstenu, completely agree. kbeatt, you need to be certain that there's not a single one of those "tons of unused database tables" that's ever going to be needed.

  6. kbeatt
    Member
    Posted 3 years ago #

    I was really hoping I would get the answer I wanted to hear. I kind of knew that I was making a lot of work for myself, but it may work out for the best if I want a clean database.

    Is it possible to export/import a single site's tables into a new installation? There are some sites with certain settings, themes, plugins, and widgets that I would like to keep in tact.

  7. Tim Moore
    Moderator
    Posted 3 years ago #

    @kbeatt: as has been said above, it's a lot of manual work directly in MySQL to do what you want. There is no easy way around it.

  8. kbeatt - You CAN do that, but again, you run into the problem of your 'unused tables.'

    Honestly, it's not that you're gonna have extraneous TABLES in your DB, but FIELDS. All those options for crap you don't use in your wp_#_options tables. That's why a fresh install isn't always a bad idea.

    (My site's been up since 1.6 and sometimes I just SHUDDER looking at the options tables)

  9. kbeatt
    Member
    Posted 3 years ago #

    @ipstenu: The FIELDS is what I am most scared of. And that's exactly why I wanted to do a fresh install.

    Am I making a bigger deal out of this than I need to? I was thinking about performance issues I am having and I just don't want to carry those over to a new server. My DB is nearing 300MB and I was thinking this would be one way to reduce it's size and add some speed back into my WordPress instance.

  10. Am I making a bigger deal out of this than I need to?

    Probably :)

    If your DB is 300 Megs, take a look at the tables themselves and see how big the wp_#_options ones are. Really the only way to scrub 'em and reboot, as it were, is to ... install fresh and rebuild.

    But. At 400 sites, I would first go through and delete the spam/unused sites.

  11. Here's some tips:

    - delete the spam blogs and users
    - turn off post revisions
    - LOOK at the db in phpmyadmin and find the biggest tables
    - clean out those wp_X_options tables, like Ipstenu suggested. there will be a LOT of transient_feeds ones you can blow away.
    - optimize that puppy
    - consider scaling them with shardb
    http://wordpress.org/extend/plugins/shardb/

    Actually, if you did that first, it might be easier to clean up 16 smaller dbs than one big one.

Topic Closed

This topic has been closed to new replies.

About this Topic