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


Who Needs Change Management?


Who Needs Change Management?

Author
Message
grobido
grobido
SSC Rookie
SSC Rookie (48 reputation)SSC Rookie (48 reputation)SSC Rookie (48 reputation)SSC Rookie (48 reputation)SSC Rookie (48 reputation)SSC Rookie (48 reputation)SSC Rookie (48 reputation)SSC Rookie (48 reputation)

Group: General Forum Members
Points: 48 Visits: 186
Comments posted to this topic are about the content posted at http://www.sqlservercentral.com/columnists/GRobidoux/whoneedschangemanagement.asp


Greg Robidoux
Edgewood Solutions
www.edgewoodsolutions.com
ckempste
ckempste
UDP Broadcaster
UDP Broadcaster (1.4K reputation)UDP Broadcaster (1.4K reputation)UDP Broadcaster (1.4K reputation)UDP Broadcaster (1.4K reputation)UDP Broadcaster (1.4K reputation)UDP Broadcaster (1.4K reputation)UDP Broadcaster (1.4K reputation)UDP Broadcaster (1.4K reputation)

Group: General Forum Members
Points: 1435 Visits: 1
Hi there

Interesting article, but lacks what the DBA's really need, that being change control templates , specific (point form) steps used in example environments and example security settings to control developers.

I am very strict with change control at all levels, no matter the garbage you hear about "extreme programming", there is no place for slackness in development. Even so, there are levels of control to suite the particular environment as not everyone is running a train control system.

Here is what I do:

Development:
+ all db schema changes are made by dba only
+ db changes are documented and analysed by dba through change control form
+ db access via roles at all times, dba manages and communicates the security paradigm clearly and checks regularly during dev cycle. Nothing goings to test or prod without following the rules.
+ developers do get ddladmin and db_security db privs for managing their views and stored procs. All objs must, at the end of the day, be owned by DBO.
+ server admin access open
+ installation of SW on any box is documented via DBA

Test:
+ change control form clearly documents schema changes
+ db backed up
+ changes applied, views/stored procs etc applied
+ app and db security privs are "what prod is like" to ensure proper testing occurs
+ server access is locked out to select few (senior analysts etc that manage integration and system testing cycles)

Prod:
DBA only.
Strict dev -> test -> pre-prod (compile server, mirror of prod) before anh change is applied.
All replace components are backed up before the change.


There is a hope range of issues etc to cover, but just some thoughts to start with.

Cheers

Chris K
www.chriskempster.com


Chris Kempster
www.chriskempster.com
Author of "SQL Server Backup, Recovery & Troubleshooting"
Author of "SQL Server 2k for the Oracle DBA"
Steve Jones
Steve Jones
SSC Guru
SSC Guru (64K reputation)SSC Guru (64K reputation)SSC Guru (64K reputation)SSC Guru (64K reputation)SSC Guru (64K reputation)SSC Guru (64K reputation)SSC Guru (64K reputation)SSC Guru (64K reputation)

Group: Administrators
Points: 64339 Visits: 19117
Nice high level article and something that I completely agree with. You need a process for managing changes.

Steve Jones
sjones@sqlservercentral.com
http://www.sqlservercentral.com/columnists/sjones
www.dkranch.net

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
grobido
grobido
SSC Rookie
SSC Rookie (48 reputation)SSC Rookie (48 reputation)SSC Rookie (48 reputation)SSC Rookie (48 reputation)SSC Rookie (48 reputation)SSC Rookie (48 reputation)SSC Rookie (48 reputation)SSC Rookie (48 reputation)

Group: General Forum Members
Points: 48 Visits: 186
Chris,
Thanks for the great input. I wasn't sure how detailed to write the article, so I did a very high level for now to get people interested. I will follow this up with future articles that give more of the process instead of just the overview of why you would want to do this.
Thanks

Greg Robidoux
Edgewood Solutions
www.edgewoodsolutions.com


Greg Robidoux
Edgewood Solutions
www.edgewoodsolutions.com
Antares686
Antares686
SSChampion
SSChampion (11K reputation)SSChampion (11K reputation)SSChampion (11K reputation)SSChampion (11K reputation)SSChampion (11K reputation)SSChampion (11K reputation)SSChampion (11K reputation)SSChampion (11K reputation)

Group: Moderators
Points: 11900 Visits: 780
I have enough Daves to tell you if I could ever get agreement on the process of this I would love it. Usually the problem is fixing something breaks something else but the person who made the changes is here 7 hours after I leave and will be out of contact for weeks. Plus it is usually a typo that gets them. Anyway nice overview.



Sebastian K. Zaklada
Sebastian K. Zaklada
SSC Rookie
SSC Rookie (37 reputation)SSC Rookie (37 reputation)SSC Rookie (37 reputation)SSC Rookie (37 reputation)SSC Rookie (37 reputation)SSC Rookie (37 reputation)SSC Rookie (37 reputation)SSC Rookie (37 reputation)

Group: General Forum Members
Points: 37 Visits: 1
Our Company has developed a tool that we think you might find useful for SQL Server Change Management. It is offered with the discount of 15%, exclusively to SQLServerCentral users (see http://www.sqlservercentral.com/products/#discounts)

SQL Source Control 2003 integrates Microsoft SQL Server with Visal Source Safe.
Thanks to this it enables source control of code and documentation of your databases.

You may also create and version database documentation quick and easy, down to table columns or stored procedure parameters, and generate documentation in easy to read and share HTML format.

To learn more about these and other features, please go to http://www.sqlsourcecontrol.com

Free evaluation version is avaliable for download at http://www.sqlsourcecontrol.com/tryit.htm



Edited by - skilledsoftware on 02/05/2003 07:24:26 AM



sincerely,
--
Sebastian K. Zaklada
Skilled Software
http://www.skilledsoftware.com
This posting is provided "AS IS" with no warranties, and confers no rights.
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