LESSON 5 — Change Management (How DBAs Avoid Breaking Production)

A “change” is anything that modifies:

• configuration

• schema

• indexes

• permissions

• jobs

• maintenance settings

• server settings

• HA/DR settings

Every professional DBA change must have:

1. Goal (what are you trying to improve?)

2. Exact change (precise steps)

3. Risk (what could go wrong?)

4. Rollback (how to undo safely?)

5. Validation (how to prove success?)

Example: “Add an index to speed up a report”

• Goal: reduce report runtime from 60 seconds to under 5 seconds

• Change: create nonclustered index on columns X, Y include Z

• Risk: increased write cost, storage usage

• Rollback: drop the index

• Validation: measure runtime before/after, watch CPU and logical reads, verify no regression

Try it now (8 minutes):
Write a change plan (Goal/Change/Risk/Rollback/Validation) for one scenario:

• “Grant access to a new user”

• “Create a maintenance job”

• “Fix a slow query with an index”