MS SQL: Mitigating schema changes/upgrades
- by bradhe
I haven't spent a ton of time researching this yet, mostly looking for best practices on upgrading/changing DB schemas.
We're actively developing a new product and as such we often have additions or changes to our DB schema. We also have many copies of the DB -- one for the test environment, one for the prod environment, dev environments, you name it. We don't really want to have to blow away test data every time we want to make a change to the DB.
s
Are there good ways of automating this or handling this? None of us have really ever had to deal with this so...
