[jasonkester]

All you really need to pull it off are:

- Change scripts for every schema change, stored in source control.

- An automated build/deploy that pulls down new change scripts and executes them in order.

- (optional) a good way to generate your backend CRUD by looking at the existing database schema, or as a lesser option an ORM that does the same thing.

So your workflow is: script out your schema change, check it in, apply it to your dev environment, regenerate the CRUD from your local schema, fix any compile errors that you've introduced. (and optionally make sure all your unit tests still pass).

You'll notice that all that stuff above is just the basic workflow you should have in place anyway.

[rbranson]

This is exactly the pattern used by Rails apps with database migrations and Capistrano deployment.