Single WP install one database – way to split into two

  • Hello,
    I have a single wordpress site running, right now I will first clean the database from old revisions and some old plugin tables etc.
    But what I wanted to ask is this:
    – this is a single wp install not multisite
    – database will get bigger each year ( even if I clean it)
    – is there a way to split database on two for example when it reach a specific limit ( two database for same domain) ?

    I googled but most topics are for multiple domains on same database, I don’t need that.

    Thanks.

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

  • Hi Chachalady,
    Not an expert but I have some experience in DB/SQL related tech and I’m hesitant to say you should do it if you don’t know what you’re doing. Do you really have that much content? Or is this a performance issue of your site and you believe “splitting” will make it faster?

    In any case, it sounds like you’re looking for load balancing – if you good something like “wordpress mysql load balancing” you should get back some results that’s more targeted to what you want.

    Articles I glanced at that looked interesting…

    https://www.severalnines.com/blog/scaling-wordpress-and-mysql-multiple-servers-performance

    https://www.digitalocean.com/community/tutorials/how-to-optimize-wordpress-performance-with-mysql-replication-on-ubuntu-14-04

    Thread Starter chachalady

    (@chachalady)

    Thank you #jsoncarter, I understand what you mean – I will take some actions only when I will be sure what to do.
    I will go and read articles you suggested.

    The site still doesn’t have performance issues, database is also under control, and I will follow the best practice and advices about cleaning up the database from old unnecessary stuff.

    It is a university site, I guess I did a good job for them since they became addicted to it .. lol … I did not expect they will post so often, they can easily be called a portal, and lately I added several extra features like plugins/custom post types for their Study Programs for example etc…
    I see how quickly the database are growing so I want to investigate what is the best way to go on.

    Soon we will do a redesign, maybe to make it active at the beginning of a 2015., maybe a stuff from 2011. and 2012. could go to one database where I can continue to put “things” from years that past, periodically, and newer data can be in currently active database ( does it make any sense at all???)
    … but I don’t want to lose SEO ranking and have “page not found” issues.
    And I haven’t got much luck on Google finding a similar topic, what do you think what would be the best way for me to prepare site to keep a good performance in the future?

    Thread Starter chachalady

    (@chachalady)

    Update: a minute I post a reply I found this topic:
    https://dba.stackexchange.com/questions/66204/how-to-split-the-wordpress-database

    They mentioned something similar:
    I would like to essentially archive out the different years of the database into separate databases so that we could still refer back to some of the data if we needed to, but decrease the size of the database for the active year.

    But the answer was not so enthusiastic ??
    They also mentioned a GigPress plugin – should I search for plugins that could help me better then learn what to do with database manually?

    I don’t recommend splitting the WordPress database into two. It is best to 1) limit the number of revisions stored and 2) use this plugin to clean and optimize your database.

    Thread Starter chachalady

    (@chachalady)

    Thank you #respectyoda for your advice. At this time I will do exactly that.
    I was looking into the future:
    – university will be here using and filling up the data year by year
    – imagine us 2020. : what to do with all that posts (news and such ..) from 2010. ?

    Let’s say main domain is myuniversity.com ,
    let’s create subdomain year2010.myuniversity.com as a separate wordpress install and database ( we can have that yearly subdomains all using that one database with separate table prefix ..)

    If I export all those posts from 2010. and import it into year2010.myuniversity.com database,the post will have different permalink then before, something like this: year2010.myuniversity.com/title-of-post

    (before it was: myuniversity.com/title-of-post )

    I just wonder if something like that is acceptable at all?

    Hmm, I understand the issue much better now. You basically have an archiving problem where the data must be readily available but you don’t want access to your “active/recent” data being slowed down by the large archived data.

    I’ve never come across this type of situation (with WordPress) but my gut feeling is that what you proposed seems a bit “ugly”. Design-wise and usability-wise.

    I believe in other situations you would have some sort of distributed back-end where when a request came in for archived data, custom code would reroute the request to the appropriate server (or you may have a no-sql type storage). I’m definitely not an expert in this area.

    Unfortunately, I don’t have any possible solutions for you ??

    Thread Starter chachalady

    (@chachalady)

    Thank you anyway – I know that my idea is not pretty design-wise and usability-wise.
    I still have time so I hope I will find some solution, maybe not perfect but at least acceptable.

    At least now I know how to better explain and describe my problem – English is not my native language so sometimes it is hard for me to explain what I am looking for …

    Thanks again.

    ok finally i found a solution for u

    its not an easy task
    but yes its will do what u need

    https://codex.www.ads-software.com/HyperDB
    https://www.ads-software.com/plugins/hyperdb/

    check those links its will helps

Viewing 8 replies - 1 through 8 (of 8 total)
  • The topic ‘Single WP install one database – way to split into two’ is closed to new replies.