By Riley Major, 2017-05-09.
For this month’s T-SQL Tuesday, James Anderson asks us to write about Shipping Database Changes.
These days all the rage is continuous deployment. Once development is “complete”, you push a button, (insert automated process here), and boom, the code is in production. I applaud shops which can reach this stage. It requires extreme devotion to automated testing and scripted processes. I haven’t worked with that sort of a system. However, many of the same principles apply to deploying the old fashioned way. Continue reading