Support » Networking WordPress » Separated Databases

Viewing 4 replies - 1 through 4 (of 4 total)
  • What are you ACTUALLY trying to do? Make a multisite instance with separate DBs per site? That’s really the antithesis of what WP Multisite is supposed to be.

    You can use the trick in the last link, but that won’t really work with Multisite itself. You can do that to have one code-base, but then you’re not Multisite 🙂

    “What are you ACTUALLY trying to do? Make a multisite instance with separate DBs per site?”
    Yes.
    “That’s really the antithesis of what WP Multisite is supposed to be.”
    I understand that.
    “You can use the trick in the last link, but that won’t really work with Multisite itself. You can do that to have one code-base, but then you’re not Multisite :)”
    won`t really work as in “break it” or as in “make it unworthy of its name”?
    😀

    Wouldn’t using separate databases save server space as the WordPress install is not repeated?

    Please use the BlockQuote tags 🙂 Makes it easier to read. So to extra blank lines between paragraphs.

    “You can use the trick in the last link, but that won’t really work with Multisite itself. You can do that to have one code-base, but then you’re not Multisite :)”

    won`t really work as in “break it” or as in “make it unworthy of its name”?

    Won’t work as in ‘Will not function from a code perspective.’

    You can do it as a single install of WP, and then you’re not using Multisite. Which I suggest you do, actually. DON’T do this with Multisite. It’s neither supported nor necessary.

Viewing 4 replies - 1 through 4 (of 4 total)
  • The topic ‘Separated Databases’ is closed to new replies.