I am still fighting to get the CODE under version control. People keep shooting themselves in the foot. Old problems keep re-surfacing, and yet, management does not see version control as anything other than a barrier to completing work.
This is mostly because the shop had a large section of code get eaten by VSS, but they will not believe that other SCM tools are not evil like VSS.
Past experience showed me a working solution:
We took the create script, and added the alters to the end. This meant that it could be run as a whole for a clean build, or only the new part could be run to facilitate migration between versions. It was a little harder to read, and a clean build looked a little odd, but we have full and useful versioning not only for installation, but for migrtation between versions as well.
Hey guys,
great article. also - i would like to recommend a great SQL server version control tool i’m using. it’s really good. you might want to check that out.