Chapter 36 Key Takeaways

1. The System Health Assessment Is the Ultimate DBA Skill

A comprehensive system review integrates every discipline covered in this book: architecture, schema design, performance tuning, security, backup and recovery, concurrency management, maintenance, and capacity planning. The ability to execute this assessment competently — and communicate the results to both technical and non-technical audiences — is the hallmark of a senior DBA.

2. Architecture Reviews Catch Configuration Drift

Production environments drift from their approved architecture over time. HADR modes get changed to address immediate issues. IP allowlists accumulate stale entries. Coupling facility policies fall out of sync with hardware changes. Regular architecture reviews catch these discrepancies before they cause incidents.

3. Catalog-Based Schema Audits Are Efficient and Repeatable

The DB2 catalog (SYSCAT views) contains everything needed to audit a schema: missing primary keys, oversized columns, redundant indexes, unused indexes, and stale statistics. These queries can be automated and run regularly as part of a database governance program.

4. Baselines Enable Diagnosis

Without a performance baseline, you cannot distinguish between "slow" and "normal." Capture baseline metrics during a representative workday. Store them. Compare them against metrics captured during stress tests, incidents, and routine monitoring. The delta between baseline and current state tells you where to investigate.

5. Stress Tests Reveal Hidden Bottlenecks

Systems that perform well under normal load may fail under peak load. Buffer pool sizing, lock configuration, sort heap capacity, log throughput, and connection limits are all resources that may appear adequate at baseline but prove insufficient at scale. Stress testing is the only reliable way to find these limits before users find them.

6. EXPLAIN Analysis Must Be Done Under Load

A query's access path may change under load due to buffer pool pressure, sort heap competition, and concurrent lock contention. EXPLAIN analysis captured during a stress test reveals the real access paths — not the idealized paths captured on a quiet system.

7. Security Audits Must Map to Compliance Frameworks

Technical security findings only matter when they are mapped to the organization's compliance requirements (PCI-DSS, SOX, HIPAA, internal policies). A finding that maps to a compliance requirement is a mandatory remediation. A finding that does not map to a requirement is an improvement recommendation. The distinction determines priority and budget.

8. Disaster Recovery Must Be Tested Under Realistic Conditions

A DR drill that always succeeds is not testing hard enough. Vary the timing, the failure mode, and the team composition. Measure RTO and RPO with actual stopwatches. Verify data integrity after recovery — do not assume it is correct.

9. Consistent Lock Ordering Prevents Deadlocks

When multiple transactions access the same set of rows, acquiring locks in a consistent order (e.g., ascending primary key) eliminates the possibility of deadlock cycles. This is a fundamental concurrency principle that applies to every database platform.

10. Capacity Planning Is a Business Function

Capacity planning is not a technical exercise — it is a business forecast with technical inputs. Growth projections come from the business (customer acquisition, new products, acquisitions). Technical analysis translates those projections into infrastructure requirements and costs. The output is an investment plan, not a configuration document.

11. Executive Communication Is a Core DBA Skill

The ability to translate "340ms lock wait time" into "3-second ATM delays for customers" is what separates a DBA who manages databases from a DBA who influences business decisions. Use traffic-light dashboards, business-impact language, and clear cost/timeline proposals when presenting to non-technical stakeholders.

12. The Capstone Report Is Your Professional Portfolio Piece

A complete system health assessment report — with findings, evidence, remediations, and executive summary — demonstrates the full range of DBA competence. Whether you use it for a regulatory examination, an internal review, or a job interview, it is tangible proof of what you can do.