Who Needs Change Management?

  • Comments posted to this topic are about the content posted at http://www.sqlservercentral.com/columnists/GRobidoux/whoneedschangemanagement.asp

    Greg Robidoux
    Edgewood Solutions

  • 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:


    + 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


    + 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)


    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.


    Chris K


    Chris Kempster
    Author of "SQL Server Backup, Recovery & Troubleshooting"
    Author of "SQL Server 2k for the Oracle DBA"

  • Nice high level article and something that I completely agree with. You need a process for managing changes.

    Steve Jones




  • 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.


    Greg Robidoux

    Edgewood Solutions


    Greg Robidoux
    Edgewood Solutions

  • 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.

  • 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

    Sebastian K. Zaklada
    Skilled Software
    This posting is provided "AS IS" with no warranties, and confers no rights.

Viewing 6 posts - 1 through 5 (of 5 total)

You must be logged in to reply to this topic. Login to reply