4 ms·

Alex at The Daily WTF wrote a great article on this subject. http://thedailywtf.com/Articles/Database-Changes-Done-Right.aspx http://thedailywtf.com/Articles/D

• penguindev 13y ago
  That's a decent read, but unfortunately even running the same precisely-versioned and ordered change scripts against dev, test, prod dbs can produce divergent results depending on the data in the db at the time. For example, prod could have a null somewhere, or data using a different url encoding flavor.... etc. (Or if you're really lucky, even the current load on the database could make it fail... i.e. transaction serialization failure due to the random row order you attempted to lock) So it should have ended with 'you're doomed'.