You can always scream loudly when database changes are requested and when it doesn't work complain bitterly that it is too hard to keep changing the database arbitrarily.

I don't necessarily recommend this, but it certainly seems to be a popular approach...

(However given the troubles of synchronizing revision control releases and databases, I'd certainly suggest that database changes should be viewed as fairly costly.)