Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I'm just starting to use subversion and if I copy the trunk to a branch to work on some new design and features. Should I create a copy of the production database. Connect to this new development database from my branch files (Zend project). Make any changes needed, such as adding new fields creating new tables etc. Then when ready to merge the branch to the trunk. Update the production db with the development db changes? If so what are some good methods to merge or update the production database? Thanks

share|improve this question
I kinda wonder if this is a better fit on This may fit under the development methodologies category. – Zoredache Dec 14 '11 at 23:58
up vote 1 down vote accepted

Schema Sync may be useful for you here. It will generate a list of all the DDL needed to modify the one database to have a schema similar to another.

If you hare making major changes besides just adding a couple fields, this may not be very useful.

What you may need to do is simply write a program/script yourself to do the upgrade. Or build yourself some kind of upgrade script that will examine the database and make changes as needed.

share|improve this answer
I find writing your own upgrade script (and SQL patches to go from one DB schema level to another) is the easiest way to go. – voretaq7 Dec 21 '11 at 17:27

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.