How do you manage schema upgrades to a production database?

Question

This seems to be an overlooked area that could really use some insight. What are your best practices for:

• making an upgrade procedure
• backing out in case of errors
• syncing code and database changes
• testing prior to deployment
• mechanics of modifying the table

etc...

Answer 1

Liquibase

liquibase.org:

1. it understands hibernate definitions.
2. it generates better schema update sql than hibernate
3. it logs which upgrades have been made to a database
4. it handles two-step changes (i.e. delete a column "foo" and then rename a different column to "foo")
5. it handles the concept of conditional upgrades
6. the developer actually listens to the community (with hibernate if you are not in the "in" crowd or a newbie -- you are basically ignored.)

http://www.liquibase.org