• Hi Robert

    Good article. This and other "change management" process/procedures are critical for ongoing successful change, when I say successful, that mean change with rollout/rollback/hotfix which all cost resources (aka money) that is vert difficult to plan for (let alone truely cost for a business).

    I follow a similar approach:

    a) develop on the DEV servers, assign base security roles

    b) script, rollout to TEST (access restricted purely to the role)

    c) formal user testing on TEST

    d) run TEST scripts against PREPROD

    e) micro test on preprod

    f) backup prod db

    g) rollout to prod

    h) minor functional testing

    Simple enough, but few sites follow it.

    Cheers

    Ck

    Chris Kempster

    http://www.chriskempster.com

    Author of "SQL Server 2k for the Oracle DBA"


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