When you are working on a software project, a Version Control System is typically used to keep track of the source code files and their changes.
But what do you do with the database related to the project?
It would be necessary to script the database schema, the changes since the previous version, as well as all the magic content that your application relies on.
Jeff Atwood over at Coding Horror (blogrolled right now) reminds us to get the database under version control, too. This post deals with versioning database change scripts. Here is a strategy to write idempotent change scripts to update your database from one version to the next.
Posted by devio 