SQL drop/backup and reload

[Akkadius]

For the purpose of test servers, I know I'm not the only one out there who's wanted to do this, and before I spend the time organizing and perfecting a process I was wondering if anyone could provide me with the same.

I'd like to be able to synch two databases up:

Meaning drop and backup all the player tables (around 20 I think) and then merge them into a test servers content build to release live. Lillu I popped in on your server to see if you had something similar as you guys use a Test Server as well.

I am posting this as I don't need this immediately but will later.

If anyone would like to share this as I know someone has a clean/quick process let me know, thanks.

[Lillu]

heya, sorry I was on phone :P

we have a test server with a recent db dump of the live server, for testing purpose. so we don't have a full db syncing between those 2 separate db, but we do have the test db's items table synced with the live db (the process is basically the same for 1 table or a full db anyways).
this is to avoid editing items on the live db, which causes the "naked bug".

the syncing is pretty simple. we use Navicat on the live server and have a remote connection from there to the test db. this way, in Navicat, you can provide two separate db as the source of the (one way) sync.

so in our example, we edit items on the test db for days, then before a live server reboot, I simply start an item table syncing between the test and the live db and the changes go live on the live server after reboot.

I might be a bit confusing, because english isn't my mother language so I appologize. Let me know if I can help you with anything else tho.

[Akkadius]

I was thinking along the lines for total content development between all tables cause I probably mess with a majoirty of them, I'm assuming you can still undergo that syncing process whilst adding the same kind of stuff?

We could be working on stuff for weeks and release the update all at once. Just trying to get ideas.

[Lillu]

thats correct, full db syncing is as much possible as a single table syncing.