> Generally when releasing new code you want to do a gradual release so that a bad release is mitigated Make each stored procedure not depend on any other proc

> Generally when releasing new code you want to do a gradual release so that a bad release is mitigated Make each stored procedure not depend on any other procedure. If you change one procedure, make sure that every existing procedure can work with both the current and the future version. Once compatible, start upgrading procedures one by one. Add in monitoring and automatic checking of the values during deployment, and you have yourself a system that can safely roll out changes slowly. I'm not advising anyone to do this, it sounds horribly inefficient to me, but it's probably possible with the right tooling.