dave.farmer (3/10/2011)

For our last release, however, another developer did the release, and while he started with a generated deployment script he couldn't be bothered to follow my established procedure (one script per DB into test, and a second after bug-fixes, so you have a part 1 and a part 2 script to run on production eventually - maybe a part 3 if the bug fixes needed further fixing) and instead hand-cranked extra items into it rather than generating a catch-up script from the testing phase... we've spent a few days tracking down and fixing the errors he introduced! Missed procedures, one procedure that was created with a rogue "drop procedure..." statement after it so every time it ran it dropped another procedure, missing static data... all manner of issues!