By Brian Fitzgerald
Introduction
This is the change control policy that I recommend for DBA organizations.
Change Policy
A production change requires these elements:
- Proof of prior testing.
- Written implementation steps.
- Written validation steps.
- A risk analysis.
- Written backout steps.
- Written approval.
Who, what, and when?
Implementation, validation, and backout instructions should identify the responsible person by name, the actual steps to be performed, and the allowable time window.
Consequences
Not adhering to change control in critical systems will eventually will lead to serious negative consequences, such as loss of data, interruption of service, unwanted public attention, reputation damage, regulatory fines, and lawsuits.
Summary
This is my recommended change policy for organizations. Administrative details depend on the organization’s culture and the change control software. Comments are welcome.