Being singularly responsible for our in-house SQL estate, I try and follow change control procedures. Nothing too radical, just a document of the change and the scripts used to deploy although on occasions, other people will do deployments and the change control steps are missed. Its quite a small company so the only person enforcing this is myself and to be honest, i can count on one hand where i've retrospectively made use of the documentation (although I'm not saying its a reason not to do it!).

I've also worked at large banks and the change control there is far too restrictive to the point where people would rather not fix an issue due to the red-tape around raising a change request. I know change is risky and banking systems are complex with many stakeholders but for many things the Change process was just far too restrictive.