SQL Clone
SQLServerCentral is supported by Redgate
 
Log in  ::  Register  ::  Not logged in
 
 
 


Change Management


Change Management

Author
Message
Steve Jones
Steve Jones
SSC Guru
SSC Guru (151K reputation)SSC Guru (151K reputation)SSC Guru (151K reputation)SSC Guru (151K reputation)SSC Guru (151K reputation)SSC Guru (151K reputation)SSC Guru (151K reputation)SSC Guru (151K reputation)

Group: Administrators
Points: 151526 Visits: 19455
Comments posted to this topic are about the item Change Management

Follow me on Twitter: @way0utwest
Forum Etiquette: How to post data/code on a forum to get the best help
My Blog: www.voiceofthedba.com
Heinrich-206378
Heinrich-206378
SSC-Enthusiastic
SSC-Enthusiastic (165 reputation)SSC-Enthusiastic (165 reputation)SSC-Enthusiastic (165 reputation)SSC-Enthusiastic (165 reputation)SSC-Enthusiastic (165 reputation)SSC-Enthusiastic (165 reputation)SSC-Enthusiastic (165 reputation)SSC-Enthusiastic (165 reputation)

Group: General Forum Members
Points: 165 Visits: 468
Having worked at a bank and retailer(both quite big) we use Change Management all the time. The change team coordinator is one of our close allies and usually assign most of the tasks to do to us.They were all ladies and very very strict. And watch out if you have deployed without approval... you might want to get that CV ready.Angry
ConnieOI
ConnieOI
SSC-Enthusiastic
SSC-Enthusiastic (150 reputation)SSC-Enthusiastic (150 reputation)SSC-Enthusiastic (150 reputation)SSC-Enthusiastic (150 reputation)SSC-Enthusiastic (150 reputation)SSC-Enthusiastic (150 reputation)SSC-Enthusiastic (150 reputation)SSC-Enthusiastic (150 reputation)

Group: General Forum Members
Points: 150 Visits: 690
My company is quite small, and we do not use any Change Management. We are part of the way there by requiring the requests for changes to be logged in our helpdesk, but that isn't done in such a way that there's any real trail to the actual changes.

There's so much to do and so little time, it's hard to initiate something like this by choice. On the other hand, it would be better to do it by choice than to have a situation where a director of the company gets involved and asks why things weren't better documented/controlled.
Michael Lysons
Michael Lysons
SSCrazy
SSCrazy (2.2K reputation)SSCrazy (2.2K reputation)SSCrazy (2.2K reputation)SSCrazy (2.2K reputation)SSCrazy (2.2K reputation)SSCrazy (2.2K reputation)SSCrazy (2.2K reputation)SSCrazy (2.2K reputation)

Group: General Forum Members
Points: 2239 Visits: 1453
We log change "requests" in our in-house change control system. It's good because we have a track of the changes made as Steve mentions. But the system isn't very granular, so it's not like a source control system for example.
paul s-306273
paul s-306273
Hall of Fame
Hall of Fame (3.6K reputation)Hall of Fame (3.6K reputation)Hall of Fame (3.6K reputation)Hall of Fame (3.6K reputation)Hall of Fame (3.6K reputation)Hall of Fame (3.6K reputation)Hall of Fame (3.6K reputation)Hall of Fame (3.6K reputation)

Group: General Forum Members
Points: 3553 Visits: 1169
We have formal change mangement procedures and stick to them all the time.

But what sort of organisation pays Change Manager more than it's senior DBAs?
richbrownesq
richbrownesq
SSC Veteran
SSC Veteran (229 reputation)SSC Veteran (229 reputation)SSC Veteran (229 reputation)SSC Veteran (229 reputation)SSC Veteran (229 reputation)SSC Veteran (229 reputation)SSC Veteran (229 reputation)SSC Veteran (229 reputation)

Group: General Forum Members
Points: 229 Visits: 150
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.



martin.whitton
martin.whitton
SSCommitted
SSCommitted (1.6K reputation)SSCommitted (1.6K reputation)SSCommitted (1.6K reputation)SSCommitted (1.6K reputation)SSCommitted (1.6K reputation)SSCommitted (1.6K reputation)SSCommitted (1.6K reputation)SSCommitted (1.6K reputation)

Group: General Forum Members
Points: 1604 Visits: 1783
I work for a medium-sized company (around 600 employees) where we have never had any formal Change Management.

We have, however, put in a system for automatically recording code changes after the event, so we can roll back if (or when!) things go wrong.

I also created a Change Log database a couple of years back. It seems as if I'm the only one who uses this with any consistency, but I like having a record of what I've done. It saves time whenever I think "I'm sure I've done something like this before", and I like the idea of having something to point to if someone says "Just what have you been doing lately?"
call.copse
call.copse
SSCertifiable
SSCertifiable (5.7K reputation)SSCertifiable (5.7K reputation)SSCertifiable (5.7K reputation)SSCertifiable (5.7K reputation)SSCertifiable (5.7K reputation)SSCertifiable (5.7K reputation)SSCertifiable (5.7K reputation)SSCertifiable (5.7K reputation)

Group: General Forum Members
Points: 5710 Visits: 2015
Small company here < 15 employees. No formal process at all. Change is managed (minimally) though and would take one of two forms depending on the project:

- Incrementing versions married to a document listing the main points about that version (that's the heavy version!)
- Release ad hoc based on change and issue tracking

With the size of the company we are lucky to get anyone beyond the developer to even look at test deployments before they go live. That's how you know it's a big and important change. Fortunately we mostly get it right - I would sometimes like a bit of help with that but what can you do? To be fair I like being fast acting and responsive - I've got used to it now.
S Hodkinson
S Hodkinson
SSCommitted
SSCommitted (1.9K reputation)SSCommitted (1.9K reputation)SSCommitted (1.9K reputation)SSCommitted (1.9K reputation)SSCommitted (1.9K reputation)SSCommitted (1.9K reputation)SSCommitted (1.9K reputation)SSCommitted (1.9K reputation)

Group: General Forum Members
Points: 1893 Visits: 1023
"However I've found that any change management quickly becomes a bottleneck devoid of common sense and full of bureaucratic nonsense."

Oh so true Steve.......'ITIL'd to death. You couldn't do anything without a reference number

Madame Artois
Christy M
Christy M
Ten Centuries
Ten Centuries (1.2K reputation)Ten Centuries (1.2K reputation)Ten Centuries (1.2K reputation)Ten Centuries (1.2K reputation)Ten Centuries (1.2K reputation)Ten Centuries (1.2K reputation)Ten Centuries (1.2K reputation)Ten Centuries (1.2K reputation)

Group: General Forum Members
Points: 1248 Visits: 221
I have worked in large companies where the change control procedure is beyond ridiculous, it takes up so much time for (as far as I can see) little benefit. The company I work in now is a mid-size firm and while we have formal change control procedures because it is a Canadian company and as such is subject to Canadian Bill 198 auditing requirements it is implemented in a sensible way. Essentially all sign-offs are held in a call system and all code changes in a source control repository. This works very well and seems to me to be a sensible and proportionate implentation of change control for what we do. It enables us to react quickly to problems that arise in the production environment and the ability to implement planned changes on our own timetable, in partnership with the business obviously.
Go


Permissions

You can't post new topics.
You can't post topic replies.
You can't post new polls.
You can't post replies to polls.
You can't edit your own topics.
You can't delete your own topics.
You can't edit other topics.
You can't delete other topics.
You can't edit your own posts.
You can't edit other posts.
You can't delete your own posts.
You can't delete other posts.
You can't post events.
You can't edit your own events.
You can't edit other events.
You can't delete your own events.
You can't delete other events.
You can't send private messages.
You can't send emails.
You can read topics.
You can't vote in polls.
You can't upload attachments.
You can download attachments.
You can't post HTML code.
You can't edit HTML code.
You can't post IFCode.
You can't post JavaScript.
You can post emoticons.
You can't post or upload images.

Select a forum

































































































































































SQLServerCentral


Search