Database shenanigans

[Pottsy]

I have a large-ish 3.8.4 forum, with mediawiki/vbwikipro on the side. My plan is to go to 4.0 eventually, but I need to sort the wiki out (and thought VaultWiki on 3.8.4 first might be a good idea).

My vb and wiki databases are separate. But it appears you need all the tables in one database for the import. How to I reliably copy the tables from one db to the other, especially given both vb and mw have tables of the same name? Server is regular LAMP.

TIA,

[pegasus]

I recommend backing up your MW database before attempting this, but you will have to rename your MediaWiki tables first:

RENAME TABLE
oldname TO prefix_oldname,
oldname2 TO prefix_oldname2,
...
etc

After this, you'll need to modify your LocalSettings.php file with your "prefix_".

If you're a coder you should be able to generate a query for this fairly easily so you don't have to type it out manually. We are considering adding the capability to import wikis from a separate database in the future, but it currently has a low priority.

[Pottsy]

Thank you - I shall have a play. And are there any issues with the transfer of tables from one db to the other?

[pegasus]

The only issues are the added load on the server during the transfer, and the storage of the tables in the same database will add somewhat to the overhead. You will probably want to remove the cloned tables after the import.

[Pottsy]

Pegasus,

Do you offer a paid service to so this? My SQL skills are not up to it.

To recap:

One database (no prefix), mediawiki 1.11.1
Another database (no prefix) vbulletin 3.8

Desired end result:

Just one database with vb and vaultwiki, with all the data imported from my mediawiki wiki.

[pegasus]

Yes, we offer a paid service to do imports. It's an addon service that you can buy from our Members area once you already have a license.