below86 (2/11/2016)
Gary Varga (2/11/2016)
below86 (2/10/2016)
...you can check in code in VCS but it isn't in production...If code is checked in early like I mention above your 'true' version 'gold' code is not what is in VCS...This is only true if you only consider the latest version is VCS. Each release (not just those that make it to production) should be retrievable as a single release. Different VCS systems use different techniques with many of them referring to labels, baseline, cuts etc. so what is in production should be retrievable using a label, for example, as should the production code for any point in time.
Ok, maybe I'll understand better when we get further into it. But using the failure happens at 3 AM and I need to look at why Stored_Proc_XX failed, I would go to the server and database that contained that stored procedure for the version I need to work on. And not go into VCS and into the prod branch and grab the last version checked in.
That can be the thin edge of the wedge...then there are tables that have changed and an index was added. Oh and have any triggers been altered? The point of viewing a release as a whole is that one doesn't get sucked into the changes one by one. You get the one and only picture. It is less clear than with compiled code but I have seen DBAs' analysis killed by a thousand updates.
Gaz
-- Stop your grinnin' and drop your linen...they're everywhere!!!