I'm a developer working in a rather simple systems/data environment: three database systems - development, testing and live. obviously as the developer I work on the development server, once my development is done (and tested), the changes are implemented on the user testing server for acceptance testing. once this is passed, the changes are implemented on the live system (used by very demanding clients).
to ensure quality, changes are not meant to be made on the live server without user testing sign-off. but sometimes this stepped is skipped by other developers and causes costly issues on the live server.
Are there any control measures you have in place at your organisation that are used to alleviate such issues?
Oh, Only the database administrators have access to databases however developers access the databases with application logins to the systems.
October 7, 2008 9:28 AM